# Get the project's push provider

Canonical page: https://docs.ovok.com/api/push/get-the-project-s-push-provider

`GET /v1/push/provider`

Returns the provider your current project sends push through, and what it is set up with. It never returns a secret.

**Scope:** the caller's project (from the token).

## Behaviour

- `provider` is `fcm`, `apns`, `expo` or `relay`, or `null` when none is set up.
- `settings` shows the setup without its secret, or `null`:
  - `fcm`: `firebaseProjectId` and `clientEmail` from the service account key.
  - `apns`: `teamId`, `keyId`, `bundleId` and `environment`.
  - `expo`: `accessToken`, whether one is stored.
  - `relay`: `url`.
- `secret` is always `null` here. A relay's signing secret is shown once, when it is set up.
- A config stored with another server's key reads as not set up; set it up again with `POST`.

## Example

```bash
curl -X GET 'https://api.sandbox.ovok.com/v1/push/provider' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk'
```

**Who can call it:** a project admin. See [roles](/access-policies#who-can-call-a-route).