Hi Gary, the problem is most likely that your devices are not registered. You can follow the steps outlined in our REST Push Guide (http://devcenter.kinvey.com/rest/guides/push) to register a device to a user.
Regarding authentication, let me clarify-- [credentials] in our guides refer to using either app, master or user credentials to authenticate your request. For more information, take a look here http://devcenter.kinvey.com/rest/guides/security#credentials
almost 9 years ago
I think I wasn't clear.
The device can receive pushes when they are sent from the web console. (/addons/push/send)
Wouldn't that mean the device is registered? How can I verify if the device is registered?
Just not when they are sent from the above end-point code.
First, you should **never** post your credentials (i.e. the ones in the Authorization header) in a public forum such as this, as this gives anyone who looks at the message access to your app. I have edited your post to remove these credentials, but to be safe, you should regenerate your master secret. You can do this by logging into the Console, going to your App Settings, and clicking the regenerate button next to the Master Secret field.
Second, you are not actually calling the custom endpoint, but rather posting a new entity to a collection called SRChirpTest. As described in our business logic guide (http://devcenter.kinvey.com/rest/guides/business-logic#invoking-endpoint), custom endpoints are accessed through:
I'm trying to call a custom endpoint from an external server.
I see this example of how to do it, and I know what everything is, however I'm not sure what to put for "[credentials]"?
POST /rpc/:appKey/custom/:endpoint HTTP/1.1