https://api.doc.securemcloud.com/api-doc/made-api/query-api/Recent content in Query API onHugo -- gohugo.ioTue, 06 Oct 2020 08:48:23 +0000https://api.doc.securemcloud.com/api-doc/made-api/query-api/query-api-intro/Tue, 13 Oct 2020 15:21:01 +0200https://api.doc.securemcloud.com/api-doc/made-api/query-api/query-api-intro/This documentation introduces users to the MADE Query API that allows them to view information assigned to various data tables. Users will be instructed on how to format requests and page through large result sets using the *range parameter. See the Authentication documentation for information on how to obtain the authentication headers within the request. Use cases # Count the number of specified items in a table. List specified items. Supported parameters # Parameter Required Definition dataSource Yes Must be set to dice.https://api.doc.securemcloud.com/api-doc/made-api/query-api/accounting-relationships/Tue, 13 Oct 2020 15:21:01 +0200https://api.doc.securemcloud.com/api-doc/made-api/query-api/accounting-relationships/This documentation describes the relationships of the accounting tables listed below. Table Role Primary Key ARCUSTMN AR customer master. AR_NUMBER ARCUSTHD AR customer financial header. AR_NUMBER ARCONTCT AR customer contacts. AR_NUMBER, LIST_NUMBER DCEMLCUS AR customer email list. AR_NUMBER, LIST_NUMBER, UNIQUE ARSUBDET Recurring billing line items. AR_NUMBER, ACCOUNT_NUMBER, BILLING_CODE_LINE ARSUBEXP Expiration overrides assigned to billing lines. AR_NUMBER, ACCOUNT_NUMBER, BILLING_CODE_LINE ARRECNTS Free-text notes attached to a recurring billing line. AR_NUMBER, ACCOUNT_NUMBER, BILLING_CODE_LINE Together, these tables provide a complete record of your accounting customers’ information.https://api.doc.securemcloud.com/api-doc/made-api/query-api/view-subscr-history/Tue, 13 Oct 2020 15:21:01 +0200https://api.doc.securemcloud.com/api-doc/made-api/query-api/view-subscr-history/This documentation explains how to view subscriber history from the Subscriber History Record (ALTRANHD) table by defining a *range on the PENDING_TIME field. It covers two use cases: continuously following (“tailing”) live history as it is written, and searching for history within a specific time frame. Because history is stored in monthly files, this documentation also covers how to target an earlier month. This guide builds on the *range paging mechanics described in the Introduction to MADE Query API documentation and returns rows from the Subscriber History Record (ALTRANHD) table.