Skip to main content

​
Bulk, Import, and Export APIs

Bulk/import APIs are designed for large link migrations and batched operational updates.

​
Bulk operation endpoints (/bulk/*)

  • POST /bulk/links/validate
  • POST /bulk/links/validate-update
  • POST /bulk/links/validate-delete
  • POST /bulk/links/create
  • POST /bulk/links/update
  • POST /bulk/links/delete
  • GET /bulk/operations
  • GET /bulk/operations/:id
  • POST /bulk/operations/:id/cancel
Use validate endpoints before create/update/delete execution to catch schema and limit errors early.
  • POST /links/bulk
  • PATCH /links/bulk
  • POST /links/bulk/delete
  • POST /links/export

​
Import endpoints (/links/import/*)

  • GET /links/import/providers
  • GET /links/import/:provider/auth
  • GET /links/import/:provider/callback
  • POST /links/import/:provider/start
  • GET /links/import/jobs
  • GET /links/import/jobs/:id
  • POST /links/import/jobs/:id/cancel
  • POST /links/import/csv
Import jobs are asynchronous and track progress/status in job endpoints.

​
Async general exports

  • POST /exports
  • GET /exports
  • GET /exports/:id
  • GET /exports/:id/download

​
Permission model

Bulk and import routes are workspace-scoped and require appropriate links permissions for read/create/update/delete operations.

​
Typical failure classes

  • validation failures on malformed rows
  • plan-limit violations during create
  • job cancellation/timeout outcomes
  • provider auth/callback failures for third-party imports
Related docs:
  • /user-guides/manual/growth/links-and-settings-reference
  • /api-reference/exports/overview