AshDeeming
commented
3 days ago Hi @hellorich If the previous app is associated to the client developer account, they can invite you as a member of that developer organisation. If however the original developer had their own account & listed the app to the customer, the customer will need to uninstall this & then install the new app once available If you require access to the developer portal as a new developer, please follow the below; https://developers.reapit.cloud/select-role
Please take a look at our FAQ's before submitting an issue, as your question may already be covered in the documentation https://foundations-documentation.reapit.cloud/faqs
Summary
I'm a developer doing work for an estate agent using Reapit. I can provide contact details to confirm this on request.
They lost access to their existing CMS as the developer had a serious accident and want to bring ownership of all hosting services and systems in house so this doesn't happen in future. I've been rebuilding these for them.
One of the final steps is to connect the Reapit API to feed properties into the CMS via the REST API for easy site population.
I can see two possible solutions:
There will be an existing Reapit app set up by the previous developer feeding content to a site - if a developer account could be set up for me and ownership of this app given to me that would be the quickest solution as I could hopefully simply change the Redirect URI(s).
If this is not possible I would need a developer account so I can reverse engineer the app set up on Reapit.
In either case, once the work is complete this account would need to be transferred to someone at the estate agents, or possibly access to the app be shared? Open to thoughts on the best way to ensure they have control over this in future.
Confirmation of this situation can be provided by a stakeholder at the estate agents on request
Thanks,
Rich
Detail and or supporting links and screenshots
Docs I've checked: https://foundations-documentation.reapit.cloud/developer-portal