Gr4vy | Operate As Docs

Connect your client's Gr4vy with a key they paste, and call its API through Operate As.

Website: gr4vy.com
Connects by: Pasting a API key
Category: Payments
Services: 1
Tools: Pass-through only

Service	Key	Base URL
Gr4vy	`gr4vy`	`https://api.sandbox.{instance}.gr4vy.app`

Your client also types their gr4vy id (The name in your Gr4vy address, such as acme in acme.gr4vy.app).

Connecting

Your client makes a API key in their Gr4vy settings and pastes it on their link. Operate As tries it with Gr4vy before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "gr4vy"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "gr4vy"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Gr4vy key you paste, with only the access you gave that key	Chosen on the provider's screen

Pass-through

Gr4vy has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.

Add the client

In Clients, add your client and select Gr4vy. Then send them their link.

Your client connects

They paste a API key from their Gr4vy settings.

Find the endpoint

Pick the call from Gr4vy's own API docs. Your path is everything after https://api.sandbox.{instance}.gr4vy.app, with the parts in braces filled in from your client's account.

Send it through Operate As

Use the client's ID, the service key gr4vy and that path. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gr4vy/transactions" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../gr4vy/transactions" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Gr4vy. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}