Odoo External API vs Pennylane

Odoo External API

One endpoint pattern reaches every model, with field selection, filters and paging, and keys that expire within three months. On Odoo Online the external API needs the Custom plan, there is no OpenAPI file, and the acceptable use policy asks for about one call a second with no parallel calls.

Pennylane

The v2 API has per-resource read and write scopes, an OpenAPI definition on every reference page, llms.txt and a breaking-change process that ran over 24 weeks. Access needs a paid Essentiel plan or partner approval, creation endpoints are not idempotent, and the API agreement lets Pennylane change or revoke the API without notice.

Odoo External API

1. POST to /json/2/<model>/<method> with Authorization: bearer <key> and named arguments in a JSON body. Add X-Odoo-Database when one host serves several databases
2. Pass fields and limit on search_read. The default limit is every matching record
3. Create invoices and bills on account.move with move_type set to out_invoice or in_invoice, then call action_post. A new move is a draft
4. Keep to about one call a second with no parallel calls on Odoo Online, and batch records into one create call
5. Ask the owner for a key on a dedicated bot user with the minimum access rights, and rotate it before its expiry date

Pennylane

1. Call GET https://app.pennylane.com/api/external/v2/me first to confirm the token, user and company context
2. Stay under 25 requests per 5 seconds per token and wait for the retry-after value on a 429
3. Do not retry a create after a timeout without checking first. Only supplier invoice imports are deduplicated
4. Send filter and sort again with every cursor. The cursor stores position only
5. Send amounts as strings such as "120.00", and ask for :readonly scopes when the task only reads
6. Use the MCP server for reads only. It cannot create, edit or delete, and firm connections need company_id