What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hi everyone, nice to join the commmunity 🙂 I'm looking for some help regarding
Hi everyone, nice to join the commmunity 🙂
I'm looking for some help regarding the REST API. The frontend facing api is very complete and well documented, we are however facing the challenge to connect an ERP/PIM to spryker; i.e. all product data needs to be WRITTEN into spryker, and orders placed by customers need to be retrieved by us for further processing (capture, pick, pack, ship, accounting/dunning, ...) which in turn requires us to also update existing orders to reflect the current status (update shipping information or attach documents like delivery slips or an invoice). We have not found any API to achieve these things - how do we get started on this?
I'm looking forward to any tips in this regard, all the best!
Comments
-
Hi Oliver!
Unfortunately there is no backoffice-facing API yet, it's in development currently AFAIK.
There is old\abandoned project (never came out of beta) though that can be adopted to your needs - https://docs.spryker.com/docs/scos/dev/sdk/zed-api/zed-api-beta.html.Another option would be to use https://docs.spryker.com/docs/scos/dev/back-end-development/data-manipulation/data-ingestion/spryker-middleware.html. But it will also require some adjustments to your needs.
0 -
As an example of the middleware you could probably use https://github.com/spryker-eco/akeneo-pim-middleware-connector.
0 -
Hi Valerii, thanks for your swift reply.
I see the Zed API is listed as Beta and includes a roadmap for future releases. Can you hint me towards more information about this?
Also, does that api already expose all the product/order and related entities or do we have to write the CRUD functionality for those in the Spryker backend aswell?0 -
includes a roadmap for future releases
I'm not aware about it. Can you share the link maybe?
0 -
It's on the very bottom of the link you sent me
https://docs.spryker.com/docs/scos/dev/sdk/zed-api/zed-api-beta.html#todos0 -
Calling it a roadmap is a bit much maybe 😄 but it reads like there are next steps planned
0 -
Ah, this. I'm not sure TBH. Will clarify internally.
But as to my knowledge, what I said already:There is old\abandoned project (never came out of beta)
backoffice-facing API ... it's in development currently
0 -
So Zed API (BETA) is an old/abandoned one.
And new Backoffice APIs (BAPI) are in development\on the roadmap.0 -
@jeremy.fourna @U02PBMFCKL0 could you guys please take a look here?
0 -
I assume this is very early state? I cannot find any reference to this at all. Is the roadmap on this public?
0 -
but it reads like there are next steps planned
The documentation has to be fixed here, sorry about misleading info there.
Other questions will be answered by mentioned gentlemen once they have time.0 -
We're also interested in that. Our use-cases would be, to connect it to Retool (https://retool.com/) or to Zendesk (so that our customer care team can see e.g. the status of an order there directly without going to the zed backend).
Especially the integration with Retool is something that should sound very appealing to be a out-of-the-box Spryker feature.
0 -
Thank you for your support, Valerii!
0 -
@U018XELUZS9 about Retool, you can create a customer suggestion about it in our portal https://spryker.ideas.aha.io/
0 -
I would just update https://spryker.ideas.aha.io/ideas/CUSTIDEAS-I-106 with this use-case. Or would you create a new idea? Because Retool basically just needs API endpoints and that's it.
0 -
As for the Back end API, we currently have 2 endpoints available (that are deprecated)
• https://github.com/spryker/product-api (Manage products)
• https://github.com/spryker/customer-api (Manage customers)0 -
About the backend API roadmap, we will communicate about it in the future, we still need to estimate some endpoints to be able to define when they could be delivered
0 -
I also see misleading these @todo definitely we should get rid of them as they do not represent any roadmap we are currently working on, I would add to Jeremy’s comments that we have 2 items right now in our kitchen one is of course the API coverage but expect also a revamping of the GLUE API architecture that would bring higher flexibility and reduce the development times
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random