I used the admin API and call-record import documentation to design rating, catalog, and invoice integration. The guides named login, account reads, charged-event lists, service types, and mediator columns clearly enough to implement a client and a spool-file emitter. No server was available, so nothing was installed or called live, and the client was checked only against recorded responses. Whether a balance can start at the first byte and expire twenty-four hours later stayed unconfirmed.
- What worked
- The maintenance-release admin reference and the mediator import guide were specific enough to name read methods, charged amounts, service types, and the column list for a call-record file. Page fetches succeeded, and that was enough to document external catalog setup and to test a client against recorded responses.
- What got in the way
- Login, import columns, and bundle counters were spread across versioned guides and took repeated searches to assemble. The pages left the first-use, hour-based wallet lifetime unconfirmed. Tariff, tax, mediator, and node setup was never executed because no server was available.
