Integrations API

36 routes across 4 controllers: the etl-ep (server-to-server access key) routes the backend serves for this family at the commit named in the front matter, plus its read-only public-ep routes, listed one table per controller. How to authenticate, send a body, page a query and read the response envelope is in the Data API reference, and the way in for a new integration is the integration path; what these records mean to the business is the E-Commerce module’s territory.

Every path is resolved from the controller’s mapping annotations; nothing here describes behaviour, because nothing about behaviour has been read — the table is what the backend serves and no more. backoffice-ep routes (the platform’s own applets, with a signed-in user’s token) and anonymous write routes are not listed; what the family serves on backoffice-ep only, and how many of its routes carry no access segment at all, is at the end of the page. A path missing from this page is not a path your access key is refused — see which reference to read.

Marketplace item listings (ecomsync items)

20 routes under /core2/tnt/dm/erp/fi/ecomsync-items (FinancialEcomSyncItemController.java).

Marketplace fulfilments

6 routes under /core2/tnt/dm/erp/gen-doc/ecomsync/fulfillments (GenDocEcomSyncFulfillmentController.java).

Payment gateways

PgwPaymentTxnHdrController

4 routes under /core2/tnt/dm/pgw/payment-txn-hdrs (PgwPaymentTxnHdrController.java).

PaymentProviderController

6 routes under /core2/tnt/dm/pgw/payment-providers (PaymentProviderController.java).

What this family does not expose over etl-ep

What follows is grouped by URL convention, and the convention does not decide which credential is accepted. The backend falls back in both directions: an etl-ep handler that finds no usable access key tries the bearer token (EndpointMethod.java:300-307), and a route reached with no Authorization header at all falls through to the access-key interceptor (TenantAuthorizationInterceptor.java:74-79). So read these lists as “no documented etl-ep path”, never as “your access key will be refused” — what still decides the outcome is the permission the handler checks.

Controllers in the same family whose routes all sit under backoffice-ep paths:

• CtosStatusRequestController — 1 backoffice-ep route (CtosStatusRequestController.java)
• CtosTransactionRequestController — 1 backoffice-ep route (CtosTransactionRequestController.java)
• CtosUserEventController — 6 backoffice-ep routes (CtosUserEventController.java)
• CtosUserHdrController — 6 backoffice-ep routes (CtosUserHdrController.java)
• CtosUserOpenQueueController — 6 backoffice-ep routes (CtosUserOpenQueueController.java)
• CtosUserStatusController — 6 backoffice-ep routes (CtosUserStatusController.java)
• CtosUserTransactionController — 6 backoffice-ep routes (CtosUserTransactionController.java)
• CtosUserController — 6 backoffice-ep routes (CtosUserController.java)
• TpyInnovatifUserEventController — 6 backoffice-ep routes (TpyInnovatifUserEventController.java)
• TpyInnovatifUserOpenQueueController — 6 backoffice-ep routes (TpyInnovatifUserOpenQueueController.java)
• SigningCloudAccountInfoController — 6 backoffice-ep routes (SigningCloudAccountInfoController.java)
• SigningCloudAddUsersController — 2 backoffice-ep routes (SigningCloudAddUsersController.java)
• SigningCloudAutoSignDocumentController — 1 backoffice-ep route (SigningCloudAutoSignDocumentController.java)
• SigningCloudDeleteDocumentController — 1 backoffice-ep route (SigningCloudDeleteDocumentController.java)
• SigningCloudDocController — 6 backoffice-ep routes (SigningCloudDocController.java)
• SigningCloudDocAttachmentController — 8 backoffice-ep routes (SigningCloudDocAttachmentController.java)
• SigningCloudDocAuditLogController — 6 backoffice-ep routes (SigningCloudDocAuditLogController.java)
• SigningCloudDocEventController — 6 backoffice-ep routes (SigningCloudDocEventController.java)
• SigningCloudDocHdrController — 6 backoffice-ep routes (SigningCloudDocHdrController.java)
• SigningCloudDocOpenQueueController — 6 backoffice-ep routes (SigningCloudDocOpenQueueController.java)
• SigningCloudDownloadDocumentController — 1 backoffice-ep route (SigningCloudDownloadDocumentController.java)
• SigningCloudGetAccountInfoController — 1 backoffice-ep route (SigningCloudGetAccountInfoController.java)
• SigningCloudGetDocumentDetailController — 1 backoffice-ep route (SigningCloudGetDocumentDetailController.java)
• SigningCloudGetDocumentListController — 1 backoffice-ep route (SigningCloudGetDocumentListController.java)
• SigningCloudManualSignDocumentController — 1 backoffice-ep route (SigningCloudManualSignDocumentController.java)
• SigningCloudQueryUserController — 1 backoffice-ep route (SigningCloudQueryUserController.java)
• SigningCloudSendAuthenticationCodeController — 1 backoffice-ep route (SigningCloudSendAuthenticationCodeController.java)
• SigningCloudUpdateCoordinateController — 1 backoffice-ep route (SigningCloudUpdateCoordinateController.java)
• SigningCloudUpdateUsersController — 2 backoffice-ep routes (SigningCloudUpdateUsersController.java)
• SigningCloudUploadCompanyImageController — 1 backoffice-ep route (SigningCloudUploadCompanyImageController.java)
• SigningCloudUploadDocumentController — 1 backoffice-ep route (SigningCloudUploadDocumentController.java)
• SigningCloudUploadSealImageController — 1 backoffice-ep route (SigningCloudUploadSealImageController.java)
• SigningCloudUploadSignatureController — 1 backoffice-ep route (SigningCloudUploadSignatureController.java)
• SigningCloudUserInfoToDocHdrLinkController — 6 backoffice-ep routes (SigningCloudUserInfoToDocHdrLinkController.java)
• SigningCloudUserInfoController — 9 backoffice-ep routes (SigningCloudUserInfoController.java)
• SigningCloudUserInfoAttachmentController — 8 backoffice-ep routes (SigningCloudUserInfoAttachmentController.java)
• SigningCloudXInnov8tifUserLinkController — 6 backoffice-ep routes (SigningCloudXInnov8tifUserLinkController.java)
• SigningCloudVerifyDocumentController — 1 backoffice-ep route (SigningCloudVerifyDocumentController.java)
• EcomSyncLabelsController — 2 backoffice-ep routes (EcomSyncLabelsController.java)
• LazadaGetDocumentController — 1 backoffice-ep route (LazadaGetDocumentController.java)
• EcomSyncShopIDController — 1 backoffice-ep route (EcomSyncShopIDController.java)
• ShopeeAuthorizationController — 1 backoffice-ep route (ShopeeAuthorizationController.java)
• GenericWebhookEventController — 7 backoffice-ep routes (GenericWebhookEventController.java)
• PayNetDuitNowController — 1 backoffice-ep route (PayNetDuitNowController.java)
• InnovatifPassportOkayDocController — 2 backoffice-ep routes (InnovatifPassportOkayDocController.java)
• InnovatifOkayFaceController — 3 backoffice-ep routes (InnovatifOkayFaceController.java)
• InnovatifOkayIdVerificationController — 1 backoffice-ep route (InnovatifOkayIdVerificationController.java)
• InnovatifOkayLiveController — 1 backoffice-ep route (InnovatifOkayLiveController.java)
• InnovatifUserAttachmentController — 8 backoffice-ep routes (InnovatifUserAttachmentController.java)
• InnovatifUserDocVerificationController — 6 backoffice-ep routes (InnovatifUserDocVerificationController.java)
• InnovatifHeaderController — 6 backoffice-ep routes (InnovatifHeaderController.java)
• InnovatifUserIdProfileVerificationController — 6 backoffice-ep routes (InnovatifUserIdProfileVerificationController.java)
• InnovatifUserVerficationController — 6 backoffice-ep routes (InnovatifUserVerficationController.java)
• RevinateContactController — 2 backoffice-ep routes (RevinateContactController.java)

And 474 routes this page does not count at all. A route reaches the tables and the lists above only when its path carries an access segment; these 474, served by controllers in scope for this page, carry none — the resource sits directly under its base path, with no /etl-ep or /backoffice-ep suffix. By the same fallback an access key reaches them too, so their absence is a limit of the classification, not a statement about what you can call. Six of the resources in that position — chart of accounts, ledgers, cashbooks, suppliers, purchase invoices and payment vouchers — are documented in full on the ERP Core API pages, with request and response bodies verified against the live API.

Related

• Webhooks — what BigLedger pushes to you, and what it does not
• Inventory API — the item master the listings point at
• API Reference — how many routes exist per family, and which have a page
• Authentication — the access key an etl-ep call carries