The fast, API fronted, SQL backed temporary data store for apps and campaigns.
Post your app or campaign data to the Flash Cache API where it'll be stored for up to 30 days.
Flash Cache over DB
Flash Cache gets your projects up and running faster and with less development overhead, removing the need for designing, building, deploying and maintaining databases for every project or platform you operate.
- Faster development - Skip database schema design, migrations, and ORM development; focus on business logic instead.
- Lower operational overhead - No need to manage backups, replication, failover, monitoring, or patching.
- Built-in scalability - Horizontal scaling, load balancing, and sharding handled automatically without re-engineering.
- Reduced expertise requirements - Junior developers can work with APIs more easily than complex SQL and connection management.
- Automatic updates - New features, performance improvements, and security patches roll out without engineering effort.
- Built-in security - Encryption in transit over HTTPS, access controls, audit logging come pre-built and included.
- Build and Burn - Build and deploy your solution or campaign, use it and burn it when done. No data retention beyond 30 days.
- No licence costs - No DB licencing costs; build database backed solutions and pay no licensing costs for your data storage.
- Plug n Play - Add data storage to any service, platform, app or website. No database knowledge required. Just plug 'n' play!
- Enterprise-level DB - Built on MySQL, Flash Cache delivers enterprise-level stability and high-speed data processing, trusted by millions of organisations worldwide for their most demanding workloads.
Limitations
- HTTP payloads are limited to 5000 bytes. Any request larger than this will result in a
400 BadRequestresponse. - You will require an Account and API Key to use the service. Encryption is enabled on a per-API Key basis.
- Your chosen
DataKeymust not contain spaces or illegal characters, it must be URL safe. - The
DataKeyis unique to the stored object. While the objects value can be changed, theDataKeycan not be changed.
HTTP Headers
The following HTTP are headers used by Flash Cache. Those identified as Request are required for the call.
Those marked as Response are returned in the HTTP response and should be checked and validated as they
contain information such as success status, record counts, error messages etc.
| Endpoint | Header | Details |
|---|---|---|
| Request | ClientId |
Unique ID for your account issued at sign-up. |
| Request | Authorization |
API Key for your App or campaign. |
| Request | ExpireInDays |
When the cache item will expire (30 days max). |
| Request | UpdateType |
u: Update only. c: Create the object if it doesn't exist.
|
| Request | DataKey |
Unique key for the cached item. |
| Response | UpdateType |
The UpdateType requested.
|
| Response | RequestId |
Unique ID for the API request. |
| Response | DataKey |
The DataKey passed in the original API call. |
| Response | Success |
Shows if the request was a success. |
| Response | ResponseMessage |
Human-readable message giving information about the request. |
| Response | ObjectUid |
Unique identifier of the newly stored object |
| Response | ExpireInDays |
When the cache item will expire (30 days max). |
| Response | Count |
The number of objects affected. |
Example Use
POST Storing data in Flash Cache
Endpoint
https://api.flashcache.uk/v1/cache/add
Request Headers
ClientId: v1:uid_79aec251cd938b1313d7f74611f2c0d1abf894f1 Authorization: v1:api_c1c9676fc333043a298551158a22ce64a2796d54 DataKey: campaign-qr-56G_new
JSON Body
{
"Campaign":
{
"Name": "QR Code",
"ID": "qr-56G_new",
"Owner": "Natasha"
}
}
Response from Flash Cache
Status Code
201 Created
Response Headers
DataKey: campaign-qr-56G_new RequestId: v1:req_4525725e314ab03c632b2712f61fff5c96207b70 ResponseMessage: Created successfully Success: true ExpireInDays: 10
PUT Updating data in Flash Cache
Endpoint
https://api.flashcache.uk/v1/cache/update
Request Headers
ClientId: v1:uid_79aec251cd938b1313d7f74611f2c0d1abf894f1 Authorization: v1:api_c1c9676fc333043a298551158a22ce64a2796d54 DataKey: campaign-qr-56G_new UpdateType: u
JSON Body
{
"Campaign":
{
"Name": "QR Code",
"ID": "qr-56G_new",
"Owner": "Anastasia"
}
}
Response from Flash Cache
Status Code
200 Ok
Response Headers
DataKey: campaign-qr-56G_new RequestId: v1:req_49308e37f40ddb9a02ba97f0489d1c131326a424 ResponseMessage: Updated successfully Success: true ExpireInDays: 10
GET Retrieving data from Flash Cache
Endpoint
https://api.flashcache.uk/v1/cache/get
Request Headers
ClientId: v1:uid_79aec251cd938b1313d7f74611f2c0d1abf894f1 Authorization: v1:api_c1c9676fc333043a298551158a22ce64a2796d54 DataKey: campaign-qr-56G_new
Response from Flash Cache
Status Code
200 Ok
Response Headers
DataKey: campaign-qr-56G_new RequestId: v1:req_d1c172ab04b5c1f394bf743c5b05a205f9e12511 ResponseMessage: Object retrieved successfully Success: true ExpireInDays: 10
JSON Body
{
"Campaign":
{
"Name": "QR Code",
"ID": "qr-56G_new",
"Owner": "Anastasia"
}
}
DELETE Deleting data from Flash Cache
Endpoint
https://api.flashcache.uk/v1/cache/delete
Request Headers
ClientId: v1:uid_79aec251cd938b1313d7f74611f2c0d1abf894f1 Authorization: v1:api_c1c9676fc333043a298551158a22ce64a2796d54 DataKey: campaign-qr-56G_new
Response from Flash Cache
Status Code
200 Ok
Response Headers
DataKey: campaign-qr-56G_new RequestId: v1:req_19bdb44c7ba386ebcda61e254f414ce618bf4727 ResponseMessage: Deleted successfully Success: true