We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a schema that gives us most of what we need to know about the objects:
https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd
It does not cover webhooks. If we are not auto-generating code from this schema, then we could at least use it to generate validation rules or tests.
The name "authorizenet-schema" feels like it would have been a better name than "authorizenet-objects" too.
The text was updated successfully, but these errors were encountered:
The schema is in many cases more up-to-date, more correct and more complete than the API reference documentation. They should be used together.
Sorry, something went wrong.
There may not be a schema for version 2.0 of the API, which is what we really need.
No branches or pull requests
There is a schema that gives us most of what we need to know about the objects:
https://api.authorize.net/xml/v1/schema/AnetApiSchema.xsd
It does not cover webhooks. If we are not auto-generating code from this schema, then we could at least use it to generate validation rules or tests.
The name "authorizenet-schema" feels like it would have been a better name than "authorizenet-objects" too.
The text was updated successfully, but these errors were encountered: