This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Minor changes in the credits transactions API endpoint
- Previous message (by thread): [atlas] Probe and firewall settings?
- Next message (by thread): [atlas] HTTP server configuration fix deployed to v3 anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Wed Jan 17 13:51:05 CET 2018
Dear colleagues,
We made some changes to the credits transactions API. The changes relate
to the use of another storage back-end.
* Transaction IDs are no longer used to retrieve the data.
* There is no detail transaction endpoint anymore, all transactions
are served as paged lists.
* The main transaction endpoint remains /api/v2/credits/transactions/
Deprecated endpoints are as follows:
* /api/v2/credits/transactions/<transaction_id>
* /api/v2/credits/transactions/admin/<transaction_id>
* /api/v2/credits/transactions/measurement/<transaction_id>
* /api/v2/credits/transactions/probe/<transaction_id>
The transactions endpoint reference is accessible at:
https://atlas.ripe.net/docs/api/v2/reference/
Best regards,
Viktor Naumov
RIPE NCC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20180117/2f2c1e11/attachment.html>
- Previous message (by thread): [atlas] Probe and firewall settings?
- Next message (by thread): [atlas] HTTP server configuration fix deployed to v3 anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]