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
Currently, a developer can only deliver payloads to the Ordinals API (from e.g. ordhook) by making a POST request with a URL that ends in a UUID, e.g. something like http://localhost:3000/api/c44a3e4c-6200-11ee-8c99-0242ac120002
This wasn't intuitive nor is it documented clearly, either in ordhook or the ordinals-api READMEs.
Request/solution: Can the workflow be such that a developer can deliver payloads to an arbitrarily-set, human-readable URL?
The text was updated successfully, but these errors were encountered:
Fixed in #277
Sorry, something went wrong.
rafaelcr
No branches or pull requests
Currently, a developer can only deliver payloads to the Ordinals API (from e.g. ordhook) by making a POST request with a URL that ends in a UUID, e.g. something like http://localhost:3000/api/c44a3e4c-6200-11ee-8c99-0242ac120002
This wasn't intuitive nor is it documented clearly, either in ordhook or the ordinals-api READMEs.
Request/solution: Can the workflow be such that a developer can deliver payloads to an arbitrarily-set, human-readable URL?
The text was updated successfully, but these errors were encountered: