Hi Peeps,
I’ve built the following, but now realise I’m missing a key feature which I need help to update.
- APP A is for a broker that creates home loans and sends them to APP B (Marketplace)
- APP B is for lenders where they can bid on the home loans they’re invited to and send their offer back to APP A
My issue is this. I’ve created two apps which work well together and share data via API using the APP Connector (API Keys), but… I’m creating a new instance (App) for each brokerage so I need APP B to recognise that when the loan has been sent from a different APP ie. C, D, E, F etc. that it sends the data back to the specific APP that sent the initial deal to it.
Does anyone know how to do this? I’m assuming there’s some method of verification required to recognise which APP the data needs to be sent to but can’t work it out.
Any help would be appreciated so much.
I guess you’ll have to build your own custom solution to manage this.
You can simply use a unique identifier to identify the App that is calling.
You’ll need to keep a record of the unique identifiers of each app in App B so you know where the call is coming from. You can even dinamically assign these IDs with an API endpoint in App B, so that it both generates a random ID and sends it back to App A/C/D… for them to store it and use it in every call.
Another option would be using the API keys themselves (as long as you have unique API keys assigned to each of the apps), but I’m unsure if you can access them dinamically from a workflow in any way.
Thank you so much, I think that in order to manage the calls dynamically I need to use the API connector instead of the APP connector which I had setup previously and was working between 2 apps.
The issue now is that I can’t seem to get the API connector to POST. It’s initializing as a POST call but when I check the APP where the data is supposed to POST to a backend workflow, it’s not making any changes.
API Connector
Backend Workflow
What am I doing wrong, the dynamic data that’s feeding is all text.
Have you debugged the workflow with Bubble log, DB log, and email?
I had been looking at the APP logs on the sending side which show below.
But then you’re right to check this, the receiving APP shows no logs so it’s not even getting there. How is it initialised but not being received?
Is it something to do with the data format in the API call? I’m so confused 
I just checked in the demo version on the initialising call, that seems to be working in the receiving APP… so it’s just the live app that doesn’t work.
Ok, i’ve been going at it and turns out it was an issue with API connector not having function to decifer between dev & live version. I took out the version-test in the endpoint and it works now. Wasn’t an issue with the data after all, it simply wasn’t feeding live to live apps.
Now I just need to run a workflow that makes the endpoint dynamic on the API call, any idea how to do that?
Glad it worked! The DEV and LIVE environments are separated. So, calls directed to the former won’t reach the latter.
Indeed, you control which eenvironment you are directing API calls to by adding/removing the /version-test part of the URL.
What are you trying to achieve?
