Re-sync Paddle payments

PATCH https://datafa.st/api/v1/admin/websites/{websiteId}/integrations/paddle

Queue a background re-sync of historical Paddle payments for this website. Use this after reconnecting Paddle or when imported payment amounts need to be refreshed. The request only queues the job; processing continues asynchronously.

Request

Path parameters

websiteId

string

Website ObjectId. From List websites (_id field). Example: 665f0b3c4d2e1a0012345678.

Response

Returns a JSON object with status: "success" and endpoint-specific fields in data.

Response fields

data[].message

string

Human-readable confirmation or status message for the operation.

Authentication

Use a dft_ account token with settings:write.

A df_ website API key for the same website can also call this route when the path websiteId matches the key's website. Write access with a df_ key is capped at member level — owner-only actions such as team management require a dft_ token and owner role.

Errors

400 — Paddle is not connected to this website.

404 — Website not found.

See API errors for the standard error envelope, auth failures, validation errors, permission errors, and rate limits.

✍️ Something missing? Suggest features.

🤖 AI agent or LLM? Read this page as markdown