canonical: https://jentic.com/apis/swaggerhub.lennert-onyx/api-access-entries # Lennert Onyx Api Access Entries API to fetch non-transmitted entries to API calling application Entries can be fetched in both XML or JSON format. The Link is https://beta.onyxone.com/restapi/siport_api_call.xml?changeStatus=1 The apikey will be provided by OnyxOne for external system Changelog: * 2.0.0 (Expected beta release: 03/10/2023, Expected live release: 03/10/2023) * * Not backward compatible change: UIN is removed from . The API exposes 4 endpoints. ## For AI agents Programmatically fetch non-transmitted entries in json format, fetch non-transmitted entries in xml format. Covers 4 operations. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Fetch non-transmitted entries in JSON format - Manage communications data programmatically - Integrate API Access Entries into automated workflows - Query and filter API Access Entries records by parameters - Monitor API Access Entries operational status and events ## Use cases ### Communications Operations Use the API Access Entries to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including fetch non-transmitted entries in json format, fetch non-transmitted entries in xml format, fetch entries in json format with cursor. Example prompt: Call GET /siport_api_call.json to fetch non-transmitted entries in json format ### Automated Entrieswithcursor.Json Management Automate entrieswithcursor.json operations by combining multiple API Access Entries endpoints. Agents can fetch non-transmitted entries in xml format and then fetch entries in json format with cursor in a single workflow. Example prompt: Call GET /siport_api_call.xml to fetch non-transmitted entries in xml format, then verify the result ### AI Agent Integration via Jentic AI agents discover and call API Access Entries endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'fetch non-transmitted entries in json format', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /siport_api_call.json | Fetch non-transmitted entries in JSON format | | GET | /siport_api_call.xml | Fetch non-transmitted entries in XML format | | GET | /entriesWithCursor.json | Fetch entries in JSON format with cursor | | GET | /entriesWithCursor.xml | Fetch entries in XML format with cursor | ## Key resources - **Entrieswithcursor.Json** — Operations for entriesWithCursor.json - **Entrieswithcursor.Xml** — Operations for entriesWithCursor.xml - **Siport_Api_Call.Json** — Operations for siport_api_call.json - **Siport_Api_Call.Xml** — Operations for siport_api_call.xml ## Why Jentic - **Setup:** Wiring API Access Entries by hand means choosing between its SwaggerHub mock host and the beta.onyxone.com backend and handling its JSON and XML entry reads yourself. Through Jentic you install once, import API Access Entries from the API Directory, and your agent calls it without you hand-building each request. - **Permission scoping:** API Access Entries exposes only read operations for access entries and carries any cursor outside the resource path, so limit the agent to the operations it needs, such as fetching entries in JSON. Every exposed operation is read-only, and you choose which of them the agent may call. - **Credential handling:** Any API Access Entries credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'fetch non-transmitted access entries in JSON', and Jentic returns the matching API Access Entries operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### What authentication does the API Access Entries use? The API Access Entries uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I fetch non-transmitted entries in json format with the API Access Entries? Yes. Use the GET /siport_api_call.json endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the API Access Entries? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I fetch non-transmitted entries in json format through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetch non-transmitted entries in json format'. Jentic returns the matching API Access Entries operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the API Access Entries have? The API Access Entries exposes 4 endpoints covering entrieswithcursor.json, entrieswithcursor.xml, siport_api_call.json operations. ### Can I limit what my agent is allowed to do with the API Access Entries? Yes. Because you run Jentic One yourself, your own rules decide which API Access Entries operations and credentials the agent may use. Every exposed operation here is read-only, so you can grant the agent just the reads it needs, such as GET /siport_api_call.json to fetch non-transmitted entries in JSON, while withholding the XML or cursor-based endpoints. The agent can only call the operations you have allowed.