> ## Documentation Index > Fetch the complete documentation index at: https://docs.paywise.de/llms.txt > Use this file to discover all available pages before exploring further. # Make > Connect paywise to your Make scenarios # paywise Make Integration The paywise app for Make connects the [Case Management API](/api-docs/case-management-api/introduction) to your Make scenarios. You can create orders and claims, read cases, report payments, download statements and start a scenario instantly when something changes in paywise, without writing code. ## Availability The paywise app for Make is available through an invite link while Make reviews it for its public app directory. To get the invite link, contact our support team at [support@paywise.de](mailto:support@paywise.de). ## Connect paywise to Make 1. In paywise, open **Für Entwickler** and create an API key. Select only the [permission scopes](/api-docs/essentials/authentication-and-environments#permission-scopes) that your scenarios need. 2. In your Make scenario, add a paywise module and click **Create a connection**. 3. Paste the API key and save. Make checks the key right away and names the connection after the key and its environment, for example `my-key (sandbox)`. **Sandbox.** Sandbox keys start with `pw_sbx_`. A connection made with a sandbox key talks to the sandbox automatically; you do not enter a URL. Build and test your scenarios with a sandbox key first. See [Sandbox](/api-docs/case-management-api/concepts/sandbox). **Scopes.** Each module needs the scope of its group, for example order scopes for the Orders and Claims modules and payment scopes for the Payments modules. A module whose scope is missing fails with a `403` error. Triggers additionally need `case:webhooks:write`, because they register a webhook endpoint in paywise. "Get API key info" shows the name, environment and scopes of the connected key. ## Modules | Group | Modules | | - | - | | Debtors | Create a debtor, Update a debtor, Get a debtor, Search debtors | | Orders | Create a draft order, Update a draft order, Delete a draft order, Submit an order, Withdraw an order, Get an order, Search orders | | Claims | Create a claim, Update a claim, Delete a claim, Get a claim, Search claims, Upload a claim document, Delete a claim document, Get a claim document, List claim documents, Download a claim document | | Cases | Get a case, Search cases, List case history entries, List case documents, Download a case document, Send a message on a case, Answer a request to client | | Payments | Report a payment on a claim, Report a payment on a case, Delete a payment, Get a payment, Search payments | | Statements | Get a statement, Search statements, Download a statement, Get a single case statement, Search single case statements, Download a single case statement | | Triggers | Watch events, Watch order decisions, Watch case status updates, Watch payments, Watch statements, Watch single case statements, Watch requests to client | | Other | Make an API call, Get API key info | "Make an API call" sends any authorized request to the paywise API. Use it for operations that have no dedicated module. ## Triggers All triggers are instant: paywise calls Make as soon as the event happens, so there is no polling interval. * **Watch events** lets you pick one or more of the case events. * The six dedicated triggers (order decisions, case status updates, payments, statements, single case statements, requests to client) have fixed events and need no setup beyond the connection. Each trigger outputs the event (`event_id`, `event_type`, `created_at`, `data`) and, where there is one, the referenced resource as `resource`, loaded with your key. For the events themselves, see [Webhook events](/api-docs/case-management-api/concepts/webhook-events). ### Webhook endpoints in paywise Creating the webhook in a Make trigger registers an endpoint whose description starts with `Make:` in paywise. Deleting the webhook in Make removes that endpoint again. A company can have up to 20 webhook endpoints. Endpoints that paywise disabled automatically after repeated failed deliveries do not count toward this limit. If creating a trigger fails with `webhook_limit_reached`, or because an endpoint for the same Make URL still exists, delete unused endpoints in the paywise portal under **Für Entwickler → Webhooks**. To change the events of **Watch events**, create a new webhook in the trigger and delete the old one on Make's Webhooks page. ## Safe retries with an idempotency key Every module that creates something has an optional **Idempotency key** field. If Make repeats a request, for example after a timeout, paywise returns the original result instead of creating a second record, as long as the key and the request are the same. If you leave the field empty, the default key changes with every run, so a retry can create a duplicate. Map a value that is unique and stable per record instead, for example your invoice number or the execution ID of the scenario combined with your own reference. See [Errors and safe retries](/api-docs/essentials/errors-and-safe-retries). ## Troubleshooting Every error message in Make ends with the paywise request ID (`request `). Include it when you contact support. | Error | Meaning | What to do | | - | - | - | | `400` `validation_error` | The request contains invalid data. The message lists the affected fields. | Fix the mapped values for the listed fields. | | `401` | The API key is invalid or was revoked. Make deactivates the scenario. | Create a new key, update the connection and switch the scenario back on. | | `403` | The key lacks the required scope. | Add the scope to the key under **Für Entwickler**, or create a new key. | | `404` | The resource does not exist or is not visible to this key. | Check the mapped ID and that sandbox and production keys are not mixed up. | | `409` | Conflict, for example the resource is in a state that does not allow the action, or `webhook_limit_reached` for triggers. | Read the message; for webhooks, delete unused endpoints (see above). | | `429` | Rate limit reached. | Make retries later. Reduce parallel runs or batch sizes if it keeps happening. See [Limits](/api-docs/essentials/limits). | ## Support If you encounter any issues or have questions about the paywise Make integration, please contact our support team at [support@paywise.de](mailto:support@paywise.de). For more information about our APIs, please refer to: * [Case Management API Documentation](/api-docs/case-management-api/introduction) * [Webhooks](/api-docs/essentials/webhooks) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.