APIHub
Back to Explore

Accounting API

The Accounting API provides unified CRUD and query access to core accounting resources—including balance sheets, bills, credit notes, customers, and company information—across integrated services.

Development
apiKeyHeader
HTTPS
CORS: Unknown
Description enriched
Visit official documentation

Latency

620ms p95

Uptime

100.0% 30d

Playground

Verified

live

Endpoints

REST · JSON
GET

/accounting/balance-sheet

Get BalanceSheet

  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • filter (query) — Apply filters
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/bills

List Bills

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • sort (query) — Apply sorting
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/bills

Create Bill

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/bills/{id}

Delete Bill

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/bills/{id}

Get Bill

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/bills/{id}

Update Bill

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/company-info

Get company info

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
GET

/accounting/credit-notes

List Credit Notes

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/credit-notes

Create Credit Note

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/credit-notes/{id}

Delete Credit Note

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/credit-notes/{id}

Get Credit Note

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/credit-notes/{id}

Update Credit Note

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/customers

List Customers

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • filter (query) — Apply filters
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/customers

Create Customer

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/customers/{id}

Delete Customer

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/customers/{id}

Get Customer

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/customers/{id}

Update Customer

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/invoice-items

List Invoice Items

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • filter (query) — Apply filters
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/invoice-items

Create Invoice Item

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/invoice-items/{id}

Delete Invoice Item

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/invoice-items/{id}

Get Invoice Item

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/invoice-items/{id}

Update Invoice Item

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/invoices

List Invoices

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • sort (query) — Apply sorting
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/invoices

Create Invoice

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/invoices/{id}

Delete Invoice

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/invoices/{id}

Get Invoice

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/invoices/{id}

Update Invoice

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/journal-entries

List Journal Entries

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/journal-entries

Create Journal Entry

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/journal-entries/{id}

Delete Journal Entry

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/journal-entries/{id}

Get Journal Entry

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/journal-entries/{id}

Update Journal Entry

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/suppliers

List Suppliers

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • filter (query) — Apply filters
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
GET

/accounting/ledger-accounts

List Ledger Accounts

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/ledger-accounts

Create Ledger Account

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/ledger-accounts/{id}

Delete Ledger Account

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/ledger-accounts/{id}

Get Ledger Account

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/ledger-accounts/{id}

Update Ledger Account

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
POST

/accounting/suppliers

Create Supplier

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/suppliers/{id}

Delete Supplier

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/payments

List Payments

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/payments

Create Payment

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/payments/{id}

Delete Payment

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/payments/{id}

Get Payment

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/payments/{id}

Update Payment

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/profit-and-loss

Get Profit and Loss

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • filter (query) — Apply filters
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
GET

/accounting/suppliers/{id}

Get Supplier

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/suppliers/{id}

Update Supplier

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/tax-rates

List Tax Rates

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • cursor (query) — Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response.
  • limit (query, limit) — Number of results to return. Minimum 1, Maximum 200, Default 20
  • filter (query) — Apply filters
  • pass_through (query) — Optional unmapped key/values that will be passed through to downstream as query parameters
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
POST

/accounting/tax-rates

Create Tax Rate

  • raw (query) — Include raw response. Mostly used for debugging purposes
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
DELETE

/accounting/tax-rates/{id}

Delete Tax Rate

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
GET

/accounting/tax-rates/{id}

Get Tax Rate

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes
  • fields (query) — The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded.
PATCH

/accounting/tax-rates/{id}

Update Tax Rate

  • id (path, required) — ID of the record you are acting upon.
  • x-apideck-consumer-id (header, required) — ID of the consumer which you want to get or push data from
  • x-apideck-app-id (header, required) — The ID of your Unify application
  • x-apideck-service-id (header) — Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API.
  • raw (query) — Include raw response. Mostly used for debugging purposes

53 endpoints auto-detected

Authentication

This API uses an API key, passed in the "Authorization" header. No OAuth required.

curl -X GET \
  "https://unify.apideck.com/accounting/balance-sheet" \
  -H "Authorization: YOUR_API_KEY"

unify.apideck.com · HTTPS only