07-30-2019 07:46 PM
11-03-2019 01:40 AM
03-26-2021 02:21 PM
+1. It would be great to have some actual S2S REST API documentation. An OpenAPI doc would be amazing but I would be happy with anything. It's very unclear what is available via the REST API.
We're currently trying to figure out if we can resolve the user org ID of all our existing users who we've only saved app-scoped IDs for up until this point. This wasn't a problem before because we were using an App Grouping but now that we're on AppLab, Rift, and Go, we needed to create a separate API service for AppLab since App Groupings aren't supported and we have no way to identify the same user between these databases. You might think we can just start sending the org ID when users log in with our backend but Go is deprecated so we can't update our client-side code to do this and it wouldn't resolve all of our existing users anyways.
03-26-2021 03:50 PM
I just found this unofficial oculus graph API repo on GitHub:
https://github.com/if1live/oculus-graph
I see some references to the profile image in the README so you could check that out. Its for GraphQL but the GraphQL API has an automatic REST wrapper. You could check out the facebook docs to see how that works. Basically, you just include "fields=name,etc" parameter on a graph node endpoint to specify which fields you want to retrieve.
Pretty unfortunate that 3rd parties are trying to document the API via brute force because Oculus doesn't provide.