Reliance onboarding allows you to create and submit an application on behalf of your customer, using information about them you have already collected. For more information, checkout our [onboarding guides](https://docs.griffin.com/docs/tags/onboarding).
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/griffin-reliance-onboarding-api"curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
openapi: 3.2.0
info:
title: Griffin API keys Reliance onboarding API
version: '1.0'
description: "## Introduction\n\nThe Griffin API is based on [REST](https://en.wikipedia.org/wiki/Representational_state_transfer).\nIt has resource-oriented URLs, accepts [JSON](https://www.json.org/json-en.html)-encoded request bodies, returns [JSON](https://www.json.org/json-en.html)-encoded responses, and uses standard HTTP response verbs and response codes.\n\nOur API deviates from strict RESTful principles if it makes sense to do so, such as when we enforce tighter access controls around certain operations.\nFor example, when closing a bank account: rather than send a PATCH request to the [bank account](#tag/Bank-accounts) resource to update it's status to `\"closed\"`, we provide a dedicated account closure resource.\n\nAnyone can [create an account](https://app.griffin.com/register) with Griffin and try out our API in [sandbox mode](/docs/guides/sandbox-vs-live-mode).\n\nNew to Griffin? Check out our [getting started guide](/docs/guides/get-started-with-the-api).\n\n## Navigation\n\nOur API is designed to be navigated programmatically. When you request any resource, you will find the URLs for related resources in the response body.\n\nThe API is structured as a tree with your [organization](#tag/Organizations) at the top. Everything that you own will be a sub-resource of your organization.\n\nTo bootstrap the navigation process, request the [index](#tag/Navigation/paths/~1v0~1index/get) endpoint: the response will contain your `organization-url`.\n\nFor a walkthrough, see our [getting started guide](/docs/guides/get-started-with-the-api).\n\n## Pagination\n\nOur list APIs support pagination (e.g. [list bank accounts](#tag/Bank-accounts/paths/~1v0~1organizations~1%7Borganization-id%7D~1bank~1accounts/get) and [list payments](#tag/Payments/paths/~1v0~1bank~1accounts~1%7Bbank-account-id%7D~1payments/get)).\nBy default, a list API returns up to 25 results. If there are more results available, the response payload will include links to the previous/next pages.\n\n### Change page size\n\nYou can request a different number of results (between 1 and 200, inclusive) by using the `page[size]` query parameter:\n\n```\nGET /v0/organizations/:id/bank/accounts?page[size]=100\n```\n\n### Navigating between pages\n\nList responses will include a `links` object with `prev` and `next` attributes, as shown below.\nPerform a GET request to the value of the attribute to fetch the previous/next page of results.\n\n```\n{\n \"accounts\": [\n // ...\n ],\n \"links\": {\n \"prev\": \"/v0/organizations/og.IG9yZ2FuaXphdGlvbi1pZA/bank/accounts?page[before]=djE6WxSPxfYUTnCU9XtWzj9gGA\",\n \"next\": \"/v0/organizations/og.IG9yZ2FuaXphdGlvbi1pZA/bank/accounts?page[after]=djE6aw79PXZySUOL16LD8HRJ3A\"\n }\n}\n\n```\nIf there is no previous or next page available, the value of the attribute will be null.\n\nAny other query parameters included in the initial request will also be included in the response payload's links.\nIf you want to change parameters (see [filtering and sorting](#section/Filtering-and-sorting)), request the first page and follow the links from there.\n\n## Filtering and sorting\n\n### Sort results\n\nBy default, resources will be listed in descending order, usually based on the `created-at` attribute.\nYou can change the sorting behaviour of a list of results by using the `sort` query parameter.\n\nFor example, to list bank accounts in ascending order (oldest first):\n\n```\nGET /v0/organizations/:id/bank/accounts?sort=created-at\n```\n\nTo _explicitly_ sort in descending order (newest first), prefix the sort attribute with `-`:\n\n```\nGET /v0/organizations/:id/bank/accounts?sort=-created-at\n```\n\n### Filter results\n\nSome list APIs allow you to filter the results.\nFilters are expressed as nested data structures encoded into query parameters.\nFor example, you can list bank accounts that are in either the `opening` or `open` state with:\n\n```\nGET /v0/organizations/:id/bank/accounts?filter[account-status][in][]=opening&filter[account-status][in][]=open\n```\n\nSimilarly, you can list legal persons with a specific `application-status`:\n\n```\nGET /v0/organizations/:id/legal-persons?filter[application-status][eq]=accepted\n```\n\n### Include resources\n\nSome list APIs allow you to include associated resources in the response, reducing the number of requests needed to fetch related data.\nFor instance, when listing bank accounts, you can include each bank account's beneficiary legal person by using the `include` query parameter:\n\n```\nGET /v0/organizations/:id/bank/accounts?include=beneficiary\n```\n\nThe response returns the usual list of bank accounts, but it will also have an `included` object with a `legal-persons` attribute:\n\n```\n{\n \"accounts\": [\n // ...\n ],\n \"links\": {\n // ...\n }\n \"included\": {\n \"legal-persons\": [\n // ...\n ]\n }\n}\n```\n\nCheck the documentation for each list API to see all options for sorting and filtering\n\n## Request limits\n\nEach organization is allowed up to 50 concurrent (in-flight) API requests. Exceeding this threshold results in a 429 - Too Many Requests response. Upon receiving a 429 response, you should implement a backoff strategy, pausing to allow your outstanding requests to complete before attempting new requests. To manage your request rate effectively and avoid surpassing this limit, consider using a controlled approach such as a finite pool of threads or workers.\n\n## Versioning\n\nThe Griffin API is versioned via a prefix in the URL.\nThe current version is v0.\nAn example endpoint is: https://api.griffin.com/v0/index.\n\nWe will not break your integration with a particular version for as long as we support that version.\nIf we release a new version, you will have 12 months to upgrade to it."
servers:
- url: https://api.griffin.com/
security:
- api-key-auth: []
tags:
- name: Reliance onboarding
description: Reliance onboarding allows you to create and submit an application on behalf of your customer, using information about them you have already collected. For more information, checkout our [onboarding guides](https://docs.griffin.com/docs/tags/onboarding).
paths:
/v0/onboarding/applications/{onboarding-application-id}:
get:
tags:
- Reliance onboarding
description: Fetch an onboarding application.
parameters:
- required: true
name: onboarding-application-id
in: path
schema:
type: string
responses:
'200':
description: ''
content:
application/json:
schema:
type: object
properties: {}
required:
- onboarding-application-status
title: onboarding-application
x-anyOf:
- type: object
properties:
onboarding-application-url:
type: string
title: onboarding-application-url
example: /v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ
description: Link to the onboarding application.
created-at:
title: created-at
format: date-time
type: string
description: ISO 8601 formatted date-time.
workflow-url:
type: string
title: workflow-url
example: /v0/workflows/wf.ICAgICB3b3JrZmxvdy1pZA
description: A link to the [workflow](/docs/terms/workflow).
legal-person-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
title: legal-person-url
example: /v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA
description: A contextual link to the [legal person](#tag/Legal-persons).
verification-url:
type: string
title: verification-url
example: /v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA
description: A link to the [verification](#tag/Verifications).
onboarding-application-status:
enum:
- processing
type: string
required:
- created-at
- legal-person-url
- onboarding-application-url
- verification-url
- workflow-url
- onboarding-application-status
title: processing
- type: object
properties:
onboarding-application-url:
type: string
title: onboarding-application-url
example: /v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ
description: Link to the onboarding application.
created-at:
title: created-at
format: date-time
type: string
description: ISO 8601 formatted date-time.
workflow-url:
type: string
title: workflow-url
example: /v0/workflows/wf.ICAgICB3b3JrZmxvdy1pZA
description: A link to the [workflow](/docs/terms/workflow).
onboarding-application-status:
enum:
- submitted
type: string
required:
- created-at
- onboarding-application-url
- workflow-url
- onboarding-application-status
title: submitted
- type: object
properties:
onboarding-application-url:
type: string
title: onboarding-application-url
example: /v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ
description: Link to the onboarding application.
created-at:
title: created-at
format: date-time
type: string
description: ISO 8601 formatted date-time.
workflow-url:
type: string
title: workflow-url
example: /v0/workflows/wf.ICAgICB3b3JrZmxvdy1pZA
description: A link to the [workflow](/docs/terms/workflow).
legal-person-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
title: legal-person-url
example: /v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA
description: A contextual link to the [legal person](#tag/Legal-persons).
verification-url:
type: string
title: verification-url
example: /v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA
description: A link to the [verification](#tag/Verifications).
error-reasons:
type: array
items:
type: string
onboarding-application-status:
enum:
- errored
type: string
required:
- created-at
- legal-person-url
- onboarding-application-url
- verification-url
- workflow-url
- onboarding-application-status
title: errored
- type: object
properties:
onboarding-application-url:
type: string
title: onboarding-application-url
example: /v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ
description: Link to the onboarding application.
created-at:
title: created-at
format: date-time
type: string
description: ISO 8601 formatted date-time.
workflow-url:
type: string
title: workflow-url
example: /v0/workflows/wf.ICAgICB3b3JrZmxvdy1pZA
description: A link to the [workflow](/docs/terms/workflow).
legal-person-url:
type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
x-anyOf:
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
- type: string
x-allOf:
- type: string
- {}
- type: object
properties:
legal-person-id:
type: string
format: ''
title: legal-person-id
required: true
name: legal-person-id
required:
- legal-person-id
title: legal-person-url
example: /v0/legal-persons/lp.IGxlZ2FsLXBlcnNvbi1pZA
description: A contextual link to the [legal person](#tag/Legal-persons).
verification-url:
type: string
title: verification-url
example: /v0/verifications/vn.IHZlcmlmaWNhdGlvbi1pZA
description: A link to the [verification](#tag/Verifications).
decision-outcome:
title: decision-outcome
type: string
enum:
- accepted
- declined
onboarding-application-status:
enum:
- complete
type: string
required:
- created-at
- decision-outcome
- legal-person-url
- onboarding-application-url
- verification-url
- workflow-url
- onboarding-application-status
title: complete
'401':
description: Requires an API key to continue
headers:
www-authenticate:
description: Returns `GriffinSession` if no valid authentication is found.
schema:
type: string
'404':
description: ''
summary: Get onboarding application
/v0/organizations/{organization-id}/onboarding/applications:
post:
tags:
- Reliance onboarding
description: "Create an onboarding application and submit it for processing.\n\n The request body must include a `workflow-url` to determine checks to be performed by the verification.\n The workflow specified determines which claims must exist for the subject profile, and any related profile (i.e. directors and people with significant control of a corporation).\n\n ---\n\n At the moment we only support 3 reliance workflows: Reliance LTD Company, Reliance Individual and Reliance Sole Trader.\n\n You need to provide different claims depending on the type of customer you wish to onboard via reliance.\n | LTD Company | Individual | Sole trader |\n | ----------- | ---------- | ----------- |\n | Subject profile:<br>`uk-company-register`<br>`trading-address`<br>`reliance-verification`<br><br>Related profiles:<br>`individual-identity`<br>`individual-residence`<br>`reliance-verification` | Subject profile:<br>`individual-identity`<br>`individual-residence`<br>`reliance-verification` | Subject profile:<br>`business-name`<br>`individual-identity`<br>`individual-residence`<br>`reliance-verification` |\n\n For more information, check out our [onboarding guides](/docs/tags/onboarding).\n "
parameters:
- required: true
name: organization-id
in: path
schema:
type: string
responses:
'201':
headers:
Location:
description: The URL of the application
schema:
type: string
description: The created application
content:
application/json:
schema:
type: object
properties:
onboarding-application-url:
type: string
title: onboarding-application-url
example: /v0/onboarding/applications/oa.b25ib2FyZGluZy1hcHBsaQ
description: Link to the onboarding application.
onboarding-application-status:
title: onboarding-application-status
type: string
enum:
- processing
- submitted
- errored
- complete
required:
- onboarding-application-url
- onboarding-application-status
title: onboarding-application-created-response
'400':
description: Responds with bad-request if the body does not conform to the schema.
'401':
description: Requires an API key to continue
headers:
www-authenticate:
description: Returns `GriffinSession` if no valid authentication is found.
schema:
type: string
'404':
description: ''
'422':
description: 'Unprocessable Entity: specific error details will be provided, if available'
summary: Create an onboarding application
requestBody:
content:
application/json:
schema:
type: object
properties:
workflow-url:
type: string
title: workflow-url
example: /v0/workflows/wf.ICAgICB3b3JrZmxvdy1pZA
description: A link to the [workflow](/docs/terms/workflow).
subject-profile:
type: object
properties:
display-name:
type: string
minLength: 1
title: display-name
description: A human readable label for an entity
claims:
type: array
items:
type: object
properties: {}
required:
- claim-type
title: claim
x-anyOf:
- type: object
properties:
aeoi-entity-classification:
title: aeoi-entity-classification
enum:
- passive-nfe
- active-nfe
- financial-institution
type: string
description: "AEOI/CRS entity classification. Submit `financial-institution`\n if the entity is a financial institution (e.g. a bank, investment fund, or insurance company).\n Submit `active-nfe` if more than 50% of the entity's gross income is active\n (e.g. trading, manufacturing, or providing services) and more than 50% of its assets are used\n to generate that active income. Submit `passive-nfe` if the entity's income is predominantly passive\n (e.g dividends, interest, rent, royalties, or capital gains) or if it is dormant."
claim-type:
enum:
- aeoi-entity-classification
type: string
required:
- aeoi-entity-classification
- claim-type
title: aeoi-entity-classification
- type: object
properties:
telephone-number:
title: telephone-number
pattern: (\+[1-9])?\d{1,14}
example: '+442012345678'
claim-type:
enum:
- alternative-number
type: string
required:
- telephone-number
- claim-type
title: alternative-number
- type: object
properties:
annual-turnover:
title: annual-turnover
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
default: GBP
value:
type: string
title: value
description: The unsigned value as a decimal-formatted string
example: '1000.00'
default: '1.00'
type: object
additionalProperties: false
claim-type:
enum:
- annual-turnover
type: string
required:
- annual-turnover
- claim-type
title: annual-turnover
- type: object
properties:
balance-sheet-size:
title: balance-sheet-size
required:
- currency
- value
properties:
currency:
enum:
- GBP
type: string
title: currency code
example: GBP
default: GBP
value:
type: string
title: value
description: The unsigned value as a decimal-formatted string
example: '1000.00'
default: '1.00'
type: object
additionalProperties: false
claim-type:
enum:
- balance-sheet-size
type: string
required:
- balance-sheet-size
- claim-type
title: balance-sheet-size
- type: object
properties:
business-address:
type: object
properties: {}
required:
- country-code
title: business-address
x-anyOf:
- type: object
properties:
street-name:
title: street-name
minLength: 1
maxLength: 50
city:
title: city
minLength: 1
maxLength: 50
postal-code:
title: postal-code
type: string
maxLength: 10
example: NW16XE
minLength: 1
country-code:
enum:
- IM
type: string
required:
- street-name
- city
- postal-code
- country-code
- country-code
title: IM
x-anyOf:
- type: object
properties:
building-name:
title: building-name
maxLength: 50
building-number:
title: building-number
maxLength: 50
required:
- building-name
- building-number
title: both building-name and building-number
- type: object
properties:
building-name:
title: building-name
maxLength: 50
required:
- building-name
title: only building-name
- type: object
properties:
building-number:
title: building-number
maxLength: 50
required:
- building-number
title: only building-number
- type: object
properties:
street-name:
title: street-name
minLength: 1
maxLength: 50
city:
title: city
minLength: 1
maxLength: 50
postal-code:
title: postal-code
type: string
maxLength: 10
example: NW16XE
minLength: 1
country-code:
enum:
- GB
type: string
required:
- street-name
- city
- postal-cod
# --- truncated at 32 KB (1010 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/griffin/refs/heads/main/openapi/griffin-reliance-onboarding-api-openapi.yml