You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each day, we get many requests for an API key for FIL Spark API data. People go to filspark.com and then request an API key with their email address.
Currently it is a manual process to send them an API key. We send one from the spark@ email address and the email looks like
Hi,
Thanks for submitting your interest in Spark data.
Your API Key is <uuid v4>
You can find integration details here: https://filspark.com/api-docs
Please reach out if you have any further questions.
Best,
Spark Team @ Space Meridian
https://filspark.com/
https://meridian.space/
Currently, we are then simply adding the API key next to their name in Slack while we wait for this ticket to be completed.
What we want
When people ask for an API key they submit a request into our tally.so account. We need to link tally.so up with mailchimp or similar to automatically generate the above email with a new UUID and send it to the provided email address. We then need to add this record to our table of API key holders so we can better monitor the usage of the API.
The text was updated successfully, but these errors were encountered:
Status Quo
Each day, we get many requests for an API key for FIL Spark API data. People go to filspark.com and then request an API key with their email address.
Currently it is a manual process to send them an API key. We send one from the spark@ email address and the email looks like
Currently, we are then simply adding the API key next to their name in Slack while we wait for this ticket to be completed.
What we want
When people ask for an API key they submit a request into our tally.so account. We need to link tally.so up with mailchimp or similar to automatically generate the above email with a new UUID and send it to the provided email address. We then need to add this record to our table of API key holders so we can better monitor the usage of the API.
The text was updated successfully, but these errors were encountered: