No "burn" API call? about onetimesecret HOT 12 OPEN

Oh, good call. I missed that while adding that feature. Will do soon.

from onetimesecret.

Just tried it out - WFM. Thanks.

from onetimesecret.

Is this API enabled on the live site?

Just tried it and i'm getting a 404.

from onetimesecret.

@chelnak Are you trying with the secret key or the private key? It's only works with the private key so that only the person that created the secret can burn it.

from onetimesecret.

from onetimesecret.

That's the one yeah.

from onetimesecret.

@delano Did some more testing this morning. The 404 happens when you try and burn a secret that has a passphrase.

Works fine when burning a secret without one.

from onetimesecret.

@chelnak Ah interesting. Thanks for the details. I need to think on this for a bit to sort what the right approach is for this case.

from onetimesecret.

@delano Thank you for adding Burn API call.
But, I have an issue. Docs say that return values are the same as Get Metadata request, which isn't quite true: you include actual Metadata-request-like data in state field of response, which's.. well, i guess not really predictable.

from onetimesecret.

As you are thinking about this, could you also think about or answer why the result from using the burn api call results in a non-flat JSON response, as in:

{
   "state": {
     "custid": "anon",
     "metadata_key": "m212lw3mqmfy21t62jeswmi940yvfkz",
     "secret_key": "",
     "ttl": 604800,
     "metadata_ttl": 604800,
     "secret_ttl": 604800,
     "state": "burned",
     "updated": 1493922248,
     "created": 1493922227,
     "recipient": []
   },
   "secret_shortkey": "j96kga"
 }

from onetimesecret.

Ha, just an oversight on my part. Thanks for the heads up.

from onetimesecret.

It still not works. Any solution?

from onetimesecret.