{"code":200,"message":"success","data":{"total":4,"items":[{"transaction_type":"CONSUME","amount":-1.0,"balance_after":7.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:17:02"},{"transaction_type":"CONSUME","amount":-1.0,"balance_after":8.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:16:38"},{"transaction_type":"CONSUME","amount":-1.0,"balance_after":9.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:15:30"},{"transaction_type":"GIFT","amount":10.0,"balance_after":10.0,"related_type":"GIFT_IN","remark":"注册赠送 10.0 Credit","created_at":"2026-04-24T17:07:26"}]}}
curl --location --request GET 'https://zylalabs.com/api/12586/api+name+-+copy+10/24189/credit+txn' --header 'Authorization: Bearer YOUR_API_KEY'
{"code":200,"message":"success","data":{"total":4,"items":[{"transaction_type":"CONSUME","amount":-1.0,"balance_after":7.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:17:02"},{"transaction_type":"CONSUME","amount":-1.0,"balance_after":8.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:16:38"},{"transaction_type":"CONSUME","amount":-1.0,"balance_after":9.0,"related_type":"AGENT_CHAT","remark":"AI Agent 对话消耗","created_at":"2026-04-24T18:15:30"},{"transaction_type":"GIFT","amount":10.0,"balance_after":10.0,"related_type":"GIFT_IN","remark":"注册赠送 10.0 Credit","created_at":"2026-04-24T17:07:26"}]}}
curl --location --request GET 'https://zylalabs.com/api/12586/api+name+-+copy+10/24190/txn+status+v1' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the API Name - Copy 10 simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
This is a example to import APIs from Postman. The description must be at least 50 characters.
The "credit txn" endpoint returns transaction details including transaction type, amount, balance after the transaction, related type, remark, and creation timestamp. The "txn-log-v2" endpoint provides transaction records filtered by parameters, including transaction ID, status, user ID, and date range, along with detailed information for each transaction.
Key fields in the "credit txn" response include `transaction_type`, `amount`, `balance_after`, `related_type`, `remark`, and `created_at`. For the "txn-log-v2" response, key fields include `transaction_type`, `amount`, `balance_after`, `created_at`, and user-related data.
The "credit txn" endpoint primarily processes transaction details submitted by users. The "txn-log-v2" endpoint accepts parameters such as `transaction_id`, `status`, `user_id`, and `date_range` to filter transaction records effectively.
The response data is structured in JSON format. It includes a `code` indicating the status, a `message` for success or error, and a `data` object containing transaction details or records, organized in an array under `items`.
Typical use cases include tracking expenses, generating financial reports, reconciling accounts, detecting fraud, and ensuring regulatory compliance. Users can leverage transaction details for personal finance management or e-commerce platforms.
Users can customize requests by specifying parameters such as transaction ID, status, user ID, and date range in the "txn-log-v2" endpoint. This allows for tailored queries to retrieve specific transaction records based on their needs.
Data accuracy is maintained through validation checks during transaction submissions in the "credit txn" endpoint. Additionally, the "txn-log-v2" endpoint allows users to filter and audit transactions, ensuring reliable records for financial analysis.
If the response contains partial or empty results, users should check their query parameters for accuracy. For the "txn-log-v2" endpoint, adjusting the date range or filters may yield more results. The API response will indicate the total count of items returned.
The "credit txn" endpoint allows you to retrieve information about credit transactions, including transaction amounts, types (e.g., CONSUME, GIFT), associated account details, and timestamps. This data is essential for tracking financial activities and managing account balances.
The "txn-log-v2" endpoint accepts parameters such as `transaction_id`, `status`, `user_id`, and `date_range`. These parameters enable users to filter transaction logs based on specific criteria, enhancing data retrieval efficiency.
The `transaction_type` field indicates the nature of the transaction, such as CONSUME for expenses or GIFT for credits received. Understanding this field helps users categorize and analyze their financial activities effectively.
The `balance_after` field shows the account balance following a transaction. This information is crucial for users to monitor their financial status and ensure accurate account management after each transaction.
Timestamps in the transaction data, such as `created_at`, allow users to track when transactions occurred. This is vital for auditing, financial reporting, and understanding spending patterns over time.
If you receive an error message, check the request parameters for accuracy and completeness. Common issues may include invalid transaction IDs or unsupported date ranges. Adjust your request accordingly and retry.
The API maintains data integrity through validation checks during transaction submissions and by providing detailed logs via the "txn-log-v2" endpoint. This allows users to verify and audit transactions effectively.
Common scenarios include tracking user spending, reconciling accounts, and conducting audits. Users can filter transactions by date or status to analyze financial behavior and ensure compliance with regulations.
O endpoint "credit txn" permite que os usuários enviem detalhes de transações de crédito, como valor, data e informações da conta. Embora não tenha parâmetros de filtragem, os dados retornados incluem informações detalhadas sobre cada transação, permitindo que os usuários analisem suas atividades financeiras após o processamento.
O campo `related_type` indica a categoria da transação, como "AGENT_CHAT" ou "GIFT_IN". Isso ajuda os usuários a entenderem a origem das transações e a categorizá-las para relatórios financeiros ou análises de gastos.
O campo `created_at` fornece o timestamp da transação, permitindo que os usuários rastreiem quando cada transação ocorreu. Essa informação é essencial para auditorias e para entender padrões de gastos ao longo do tempo.
O endpoint "credit txn" suporta transações de crédito, incluindo tipos como "CONSUME" para despesas e "GIFT" para créditos recebidos. Isso permite que os usuários monitorem tanto gastos quanto ganhos em suas contas.
O campo `amount` indica o valor da transação, podendo ser positivo (créditos) ou negativo (despesas). Compreender este campo é crucial para a gestão financeira, pois ajuda os usuários a monitorar seu saldo e gastos.
O endpoint "txn-log-v2" fornece registros detalhados de transações, incluindo informações como ID da transação, status, montante e dados do usuário. Isso é útil para auditorias e reconciliações financeiras.
Os usuários podem auditar transações filtrando por parâmetros como `transaction_id`, `status` e `date_range`. Isso permite uma análise detalhada e a verificação de transações específicas, garantindo a conformidade e a precisão dos registros.
As respostas dos endpoints seguem um padrão JSON, contendo um `code`, uma `message` e um objeto `data`. O `data` inclui detalhes das transações ou registros, organizados em um array sob `items`, facilitando a interpretação e o uso dos dados retornados.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund