Thanks for the opportunity to review and ask questions.
This feels like one of several 'Agent Service/management' API's that would be needed for this draft endpoint to be useful.
Whats the plans for those? (the draft roadmaps didn't seem to cover them)
What does this API offer software developers, that cannot be done on the HMRC UI (beyond a software developer being able to put their own UI on an HMRC workflow/process)
eg, is it bulk processing?
or the ability to do the same thing per client from software, that we can do on the HMRC site/HMRC UI?
Would an agent/practice MTD client list be more useful as a first step than this? Here are your clients, Here's who is on MTD for what?
How does the authorisation work? (Is it the same MTD Token we use in software? or different)
Would the API call use the API limits for us as a software vendor or be seperate? (if I have 150 clients, and I want to do something for all of them at the same time....there's my limit gone on the token for that minute..)
Would we be able to use the API to retrieve the status of an authorisation initiated through the HMRC web ui ? Or only authorisation status initiated via the API?
Same question for web UI. Would that show authorisations in progress/status initiated via the API?
Whats the potential development timeline for this API (roadmap only shows TBD)
When will we be able to test agent authorisations outside of MTD live scenarios...this is THE most pressing agent issue right now.
thank you for finding time to review our proposal, we value your contribution.
Can you provide some more detail on the other type of Agent Service or Management API’s you would like to see?
Our API provides the same invitations functionality as the HMRC UI. This is to allow 3rd parties to fully integrate this functionality into their software.
There are no plans to introduce a MTD Client List API. Our expectation is that client lists will be managed by the end client software and will not be provided us.
You will be able to check the status of invitations created in the UI and vice versa.
We will support the same token to authorise the software providing Agents Auth at the time we deliver implementation in the Sandbox.
The API call would use the API limits for the application and therefore if you want to do something for all of them at the same time via the same application you will use up the limit.
We don’t have a confirmed release date yet but our plan is to deliver it Q3 / Q4 this year, but this is subject to change.
Thanks for the opportunity to review and ask questions.
This feels like one of several 'Agent Service/management' API's that would be needed for this draft endpoint to be useful. Whats the plans for those? (the draft roadmaps didn't seem to cover them)
What does this API offer software developers, that cannot be done on the HMRC UI (beyond a software developer being able to put their own UI on an HMRC workflow/process) eg, is it bulk processing? or the ability to do the same thing per client from software, that we can do on the HMRC site/HMRC UI?
Would an agent/practice MTD client list be more useful as a first step than this? Here are your clients, Here's who is on MTD for what?
How does the authorisation work? (Is it the same MTD Token we use in software? or different)
Would the API call use the API limits for us as a software vendor or be seperate? (if I have 150 clients, and I want to do something for all of them at the same time....there's my limit gone on the token for that minute..)
Would we be able to use the API to retrieve the status of an authorisation initiated through the HMRC web ui ? Or only authorisation status initiated via the API?
Same question for web UI. Would that show authorisations in progress/status initiated via the API?
Whats the potential development timeline for this API (roadmap only shows TBD)
When will we be able to test agent authorisations outside of MTD live scenarios...this is THE most pressing agent issue right now.