
Before the meeting
- Read their documentation, and try the API once if there is a test environment.
- Write down the three or four calls you think you need, in the order you will make them.
- Bring one example of the data you will send and the answer you expect back.
With that on the screen, the meeting is about your use of their API, not a general tour of it.
The contract
- What are the limits: requests per second, the size of a request, the size of a page of results?
- What does each error mean, and which ones are safe to retry?
- Is the call safe to repeat? If a reply is lost and we send it again, does it happen twice?
- How do we page through a long list, and is the order stable while we do?
Change
- How are versions handled, and how long is an old version kept?
- How much notice do we get before a breaking change, and where is it announced?
- Has a change ever broken a team like ours? What happened?
Events
- Is there an event or a webhook for what we would otherwise ask for every minute?
- Is it signed, and can it arrive twice or out of order?
- What happens to events sent while our side is down?
Running it
- Who is on call for it, and how do we reach them during an incident?
- Where is its status shown?
- Does the test environment behave like production, including the limits?
Leave with three things written down
- The calls you will use, each with its limits.
- The errors you will handle, and what you will do for each.
- The name of a person to ask, and the channel to ask in.
Send the list to the other team the same day and ask them to correct it. Their corrections are the most useful part of the meeting.