Unfortunately they're giving 201 on the first call which just gives you parameters and the address to fetch the invoice from I guess that creates a unique internal code.
That second call could legitimately be 201 as it creates a unique invoice. But 201 on the first information only call is a bit weak.
In the absence of a tight spec you get this kind of interop problem.
Brian of London / Sir Brian of London
npub18h…wfmgv
2023-04-16 15:07:47
in reply to nevent1q…qz6w
Author Public Key
npub18hz8xs2tafx7rhclzukrr94gypcemw6ch2hcwe9eak4q03k4a8wq2wfmgvPublished at
2023-04-16 15:07:47Event JSON
{
"id": "e6f9cdb77f37019585e08f9ca0a2053aef3fcb41e50db4ebcb34e7c1b38452a9",
"pubkey": "3dc473414bea4de1df1f172c3196a820719dbb58baaf8764b9edaa07c6d5e9dc",
"created_at": 1681657667,
"kind": 1,
"tags": [
[
"e",
"9871f1a510304e7ced55e476af8a548cbbb1124bf4e1f4ec8d029eebbb92c0f1"
],
[
"e",
"cec3f8202c33eb1358463511a95f869eca4549eec31a9c09637fa20cb533f07d"
],
[
"p",
"883fea4c071fda4406d2b66be21cb1edaf45a3e058050d6201ecf1d3596bbc39"
],
[
"p",
"0b1aef6f7eb29eb2b6654279f3ce86e768461c7b434aee7ce70028d348eff84c"
]
],
"content": "Unfortunately they're giving 201 on the first call which just gives you parameters and the address to fetch the invoice from I guess that creates a unique internal code. \n\nThat second call could legitimately be 201 as it creates a unique invoice. But 201 on the first information only call is a bit weak. \n\nIn the absence of a tight spec you get this kind of interop problem.",
"sig": "a1b52765dde0323716f12e88e3d683abd0da6b17e3a75ae72e4076b7967aefb045e2bda2437d21361907216d8fe7ce1580cb7983a8b3ed1b34805ad0846ca61e"
}