Hi Team, I want Api reference. for backend access using spryker API i want to create custom Backoffice. Please Guide me for the same.

There is no API exposed for the Backoffice. While you could build your own Backoffice API based on the Backend Glue API it would require an high amount of effort. But why would you implement your own backoffice anyway? Is there anything missing or any benefit you see by reimplementing the backoffice based on API and, I assume, a Single Page Application? Not only will this require a high effort to implement, but also a very high maintenance cost compared to the current backoffice that is maintained by Spryker. I would really challenge this requirements if it aroused in a project as probably the invest is not worth the benefits. But maybe you can share a little more context why you want to build your own backoffice.

i am creating headless application using spryker api and now i want to admin application as well so that we will not go to web always

i want to admin application as well

But IMO there needs to be a good reasoning for spending that much time/effort for a feature that already exists.

yeah i am agree but its the requirement to have backoffice api as well same as we have created frontend application using spryker api

Ok, the following resources will help you creating a Backoffice API: • https://docs.spryker.com/docs/scos/dev/glue-api-guides/202307.0/backend-and-storefront-api-module-differences.html • https://docs.spryker.com/docs/scos/dev/glue-api-guides/202307.0/decoupled-glue-api.html#resource-modules • https://docs.spryker.com/docs/scos/dev/glue-api-guides/202307.0/routing/create-backend-resources.html There are already a few backend API implementations you might want to use for a backoffice API: https://github.com/spryker?q=backend-api&type=all&language=&sort= Especially https://github.com/spryker/dynamic-entity-backend-api/tree/master should be interesting for you as a generic entry point for Create/Update/Reade/Delete operations

Hi, i am requiring product backend api but facing version issue what i should do

Composer is already telling you what the issue is (

spryker/product-backend-api

requires

spryker/category >= 5.10

but you only have

spryker/category = 5.7

). In this case you could try to update

spryker/category

as well (

composer update spryker/category && composer require spryker/product-backend-api

. I can imagine that Spryker is a very complex stack in the beginning, but it would be good to read and understand error messages/notices first as it will give you the possibility to solve your issues on your own, instead of asking here. Don't get me wrong, I'm happy to help with most problems, but I see that most of the time the questions could easily be solved by reading and understand the error message or have a look into the documentation, but there is a tendency to ask here first, which may be faster for you but a waist of time for the one that answers the question. Imagine I would charge you, let's say $50, per answer. Would asking the question still be the first option that comes to your mind? There are a lot of things that are not obvious or were input from the community is necessary, then I'm, and probably others here too, happy to answer those.

Yeah i understand. but i have updated spryker/category and spryker/product already also i have tried composer update but my code crashed. so back to first step i have asked you again.