As many solutions born in hyperscalers for hyperscalers needs, having a lot of investment, voice, code, they get a lot of visibility and traction (coolness), segues that can happen that they are applied outside their native domain of modelling and application and problem space.
GraphQL data domain exposes some domain concept in graphs, you query the fields you need or the item you need, you "use mutators" to set/act on something.The service site should document the data model.You need to learn the basic GraphQL syntax. I can suggest to experiment first via the online tools for quick turnover.
Personally, I never used it in IBMi systems (but technically is a POST with your JSON query and you get your result JSON back).
my 2c
On Friday, January 23, 2026 at 03:46:55 PM GMT+1, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks for confirming my understanding. Seems like overkill for a marketplace platform...
The problem I see is that the "query" needs to indicate each node I want returned. Yet the documentation doesn't describe what nodes are available.
IMHO it's much easier if I just ask for orders and the API gives me everthing - not as efficient, but we're talking bytes not megabytes or gigabytes of data.
The query language is what I have a problem with...
AI says I can use HTTPAPI as follows:
request = '{"query": "query { invoices(filters: {notDispatched: true}) ' +
'{ nodes { id legacyId statusFlags } } }"}';
response = http_string('POST': url: request: 'application/json');
thx again,
Greg
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of cesco via MIDRANGE-L
Sent: Friday, January 23, 2026 5:17 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: cesco <emaxt6@xxxxxxxxx>
Subject: Re: Marketplacer API (GraphQL)
GraphQL is yet another thing invented to resolve some "REST" problems ( that 99% of times is called that way but is luckily just many times RPC over HTTP carrier) and if I recall correctly introduced by Facebook to optimize the fetching from their frontend heavy stuff to backends.Think of it as query that you send and you get data back.The result would be a perfect match I think for a RPG DS in DS mapping (i.e. a graph like structure).
Usually is HTTP + JSON.Normally one would use a "client" layer to query the interface to abstract some details.
Back to IBMi (if RPG) I think one could send just the HTTP POST with the query to the GraphQL and work with the results.
On Friday, January 23, 2026 at 04:10:05 AM GMT+1, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hoping someone else has encountered this platform... one of our customers is moving from a REST-based API (Mirakl) to this GraphQL based API (Marketplacer).
I have worked with SOAP and REST APIs in the past, but have zero experience with GraphQL. I'm having a hard time following the documentation and Postman examples.
TIA,
Greg
[Logo]<
https://protect.checkpoint.com/v2/r01/___https://www.totalbizfulfillment.com/___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OjkyNjY6NWEwY2IxMzQ4OTc0ZTAyZGNmMDUxN2M3MjE1M2IzNzY4YmIzYWJhYWI1MzRkM2I1MTY0NzFiZjRhNDFiYjE2ZjpwOlQ6Rg> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
https://protect.checkpoint.com/v2/r01/___www.totalbizfulfillment.com___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OjlkNzM6YTEzNjYwYjk2NzIyYTgzNjIyM2I1ZWVjMjI0MWQ4ODkzNDljOTdlZTRiODllOTA1MDlmYzQ5MTY0N2RmZDMwYzpwOlQ6Rg<
https://protect.checkpoint.com/v2/r01/___http://www.totalbizfulfillment.com___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OjBjZDU6MjIwMTFiNTY4Yzc2ZmYyNjJkZDY4NjJiNjFlMDNhMzJmNzgyYzcwYWM3M2Y5OTdjNzgzMjdhMmIxY2FmMGU4MzpwOlQ6Rg>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://protect.checkpoint.com/v2/r01/___https://lists.midrange.com/mailman/listinfo/midrange-l___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3Ojk5NDQ6OTU5ZDI0NjE2OTRjMGI0ZDBkODdmNDQwMWQwMGY3Zjk1NjIxNDlhM2MxNmUwNjg3YWQwMzA3MWQ3ZDBiMjM5NTpwOlQ6Rg
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://protect.checkpoint.com/v2/r01/___https://archive.midrange.com/midrange-l___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OjViZmE6NDE4ZDZiMTkxYTJjYTNhMzVmZmFjODUxNDcyZjk0MjQzYzFkMmIxYmUzMDQyNDA5NWRhMDAzNjFkYzIwMDk2MzpwOlQ6Rg.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://protect.checkpoint.com/v2/r01/___https://lists.midrange.com/mailman/listinfo/midrange-l___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OmE4YzY6YWJmZjlhMTJkNjlmODkxMDM4MTJkOTk1NmUwZjA3YWY2ZGZhZGE3N2E1NzZiYjYyNGIwMDI4MDY0MDkxNDIwZTpwOlQ6Rg
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://protect.checkpoint.com/v2/r01/___https://archive.midrange.com/midrange-l___.YzJ1OnRvdGFsYml6ZnVsZmlsbG1lbnQxOmM6bzpjM2JhZDEzOTNjNjQ0NDBiZTcyY2E5NjI4MjgwOTZkZDo3OmFjNTQ6NzFiMzhiZGY1ZTc5NzA5MzE1MzE5NmIyMTU3ZDQzYWExYmYxMWMwOTA0ZWI5MDllODY5MjEyY2ZhZmQ0YjNjMjpwOlQ6Rg.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Greg Wilburn
Director of IT
301.895.3792 ext. 1231
midrange.com
