---
title: "Processes callback URL"
method: POST
path: "/services/microsoft_business_central_custom/oauth-process-callback"
tags: ["services.microsoft_business_central_custom"]
---

# Processes callback URL

`POST /services/microsoft_business_central_custom/oauth-process-callback`

## Request

- Base URL: `https://headless.dataddo.com/customer-api/v1`
- URL: `https://headless.dataddo.com/customer-api/v1/services/microsoft_business_central_custom/oauth-process-callback`
- Auth: none required

## Request body

- object
  - `callbackUrl` string
  - `config` PostAuthorizerMicrosoftBusinessCentralCustomInput
    - `label` string: Your own textual label for the document. By using labels you can easily identify your documents later.
    - `tenant_id` string
    - `scopes` string[]: Array of strings.
    - `client_id` string
    - `client_secret` string
    - `redirect_uri` string

## Response `200`

New service

- MicrosoftBusinessCentralCustomUserAuth
  - `customer_id` string: The id of the customer (account) the document belongs to.
  - `member_id` string: The id of the member (user) who created the document.
  - `label` string: Your own textual label for the document. By using labels you can easily identify your documents later.
  - `external_id` string, nullable: The id of the document in external systems. By setting external_id you can link document with external systems id.
  - `is_locked` boolean: You may mark the document as locked to prevent accidental changes. When locked, the document cannot be modified or deleted.
  - `status` boolean: The current status of the authorizer. True if the authorizer is operational, false otherwise. When the authorizer is marked as broken (false), it indicates that the authorizer is not functioning properly and may require running test connection or changing the configuration values of such authorizer.
  - `status_detail` string: A detailed message providing additional information about the status of the authorizer. This field can be used to provide more context or troubleshooting information when the authorizer is marked as broken (false).
  - `service_type` string: This field specifies the type of the authorizer, which can be either "template" or "redirect". The "redirect" means that the authorizer requires a redirect to a third-party service for authentication. When "template" all the fields are defined statically in dataddo.
  - `last_use` integer, nullable: The timestamp (in seconds) of the last use of the authorizer. The last_use is updated on every use when the authorizer is used for authentication.
  - `identifier` string: The identifier of the authorizer. This field is used to uniquely identify the authorizer. Useful in case when there are multiple authorizers to the same service (e.g. with different user names etc).
  - `hash` string: The hash of the authorizer settings values. Regenerated on every change of the authorizer settings. May be used to uniquely identify the authorizer and check for authorizers with duplicate settings.
  - `created_at` integer: The timestamp (in seconds) of the time when the the authorizer was created
  - `updated_at` integer: The timestamp (in seconds) of the time when the the authorizer was updated for the last time
  - `id` integer
  - `type` string
  - `client_id` string
  - `client_secret` string
  - `redirect_uri` string
  - `tenant_id` string
  - `scopes` string[]: Array of strings.

---

[API](https://skmtc.dev/dataddo/apis/dataddo-headless-beta-api.md) · [All operations](https://skmtc.dev/dataddo/apis/dataddo-headless-beta-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dataddo/apis/dataddo-headless-beta-api/revisions/dcfa2345bd10?raw)