Several attributes lack helpful descriptions (examples: transId and transactionSrc)

[SeanKilleen]

In the API spec, many of the field descriptions are just a repeat of the field names.

For example, within the tracking API, in the tracking method, the transId and transactionSrc headers are required, but there's no description of what those fields actually mean or why they're required -- just a repeat of the field names.

Can someone clarify what these fields mean? Happy to submit a pull request to update the description once we understand more.

[elidrissidev]

I think they just missed it for that endpoint, the description of those fields is mentioned in other places like Pickup Rate, it says:

• transId: An identifier unique to the request. Length 32.
• transactionSrc: An identifier of the client/source application that is making the request.Length 512. (kinda like a user-agent)

[SeanKilleen]

@elidrissidev thanks for that! I'll submit a PR for this now, just in case it can be helpful for others.