# Fibery has an RPC API and a GraphQL API, but no REST API

**URL:** <https://community.fibery.io/t/fibery-has-an-rpc-api-and-a-graphql-api-but-no-rest-api/6557>\
**Category:** API & Programming\
**Created:** [August 27, 2024, 1:07pm UTC](https://community.fibery.io/t/fibery-has-an-rpc-api-and-a-graphql-api-but-no-rest-api/6557 "2024-08-27T13:07:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jean1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jean1/32/1669_2.png) [@jean1](https://community.fibery.io/u/jean1)\
**Post date:** [August 27, 2024, 1:07pm UTC](https://community.fibery.io/t/fibery-has-an-rpc-api-and-a-graphql-api-but-no-rest-api/6557/1 "2024-08-27T13:07:38Z")

</div>

I had a look at [. | Fibery](https://the.fibery.io/@public/User_Guide/Guide/REST-API-259)  
It’s a perfectly fine API, but why would you call it a REST API?  
It’s a classic RPC API: there is one endpoint `/commands`, to which you `POST` batches of datalog-style code.

Though it’s true that [REST](https://en.m.wikipedia.org/wiki/REST) is mostly used rather loosely on the web today, it does have a defined meaning. At its most basic, I’d say it means “not RPC” 😜

I recommend calling it an RPC API. This correctly characterizes the design and helps to correctly set expectations.