tebarDocs
PanduanDeveloperAPI ReferenceChangelog
Connect

List allowed redirect origins

GET
/v1/connect/redirect-origins

Requires the read scope. Owner key or session only: a profile key gets 403 owner_key_required.

Authorization

bearer
headerAuthorizationBearer <token>

An API key (tb_live_...) from the dashboard, or an OAuth access token.

Response Body

The allowlist.

application/json
  1. response
data*array<>
Example Request
curl -X GET 'https://api.tebar.app/v1/connect/redirect-origins'
Example Response
{
  "data": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "origin": "string",
      "created_at": "2019-08-24T14:15:22Z"
    }
  ]
}

Create a connect link POST

A page where your client connects their accounts into the profile ({id} may be its external_id). redirect_url's origin must be allowed in /v1/connect/redirect-origins (422 redirect_origin_not_allowed); state comes back unchanged. Requires the write scope. Owner key or session only: a profile key gets 403 owner_key_required.

Allow a redirect origin POST

Scheme and host (and port), e.g. https://app.example.com; at most 20. Requires the write scope. Owner key or session only: a profile key gets 403 owner_key_required.