Oct 2012
2 / 3
Oct 2012
Oct 2012
sajanm
Oct '12

Hi,



I want to integrate E-junkie data to a small application that I am developing. I put the url in the settings, and have been receiving the POST data accordingly. I am in a trial phase, so I dont have cash for my test products. I have assigned "stored codes" to be sent with every download of the product. Since the price of the item is 0, e-junkie doesnt allow the user to change the quantity of purchase, even though I have enabled sending stored codes.

(I have enabled allow buyers to change quantity)



I have tested the order data for the following scenario: 2 products with 1 quantity each.

POSTed order data is seen as

num_cart_item = 2

[item_name1] => Picture 2

[item_number1] => XXXXX

[mc_gross_1] => 0

[quantity1] => 1

[key1] => XXXXXX

[item_name2] => Picture 1

[item_number2] => XXXXX

[mc_gross_2] => 0

[quantity2] => 1

[key2] => XXXXXX



Now I wanna know how the order data will look like if I have 2 product with 2 quanties each.



If E-junkie allowed ur to change quantity for products with price 0 that sends generated code, that would be great.

  • created

    Oct '12

  • last reply

    Oct '12
  • 2

    replies

  • 1.6k

    views

  • 2

    users

E-junkie_GuruWebmaster & Support Guru
Oct '12

We only allow quantity=1 for free products as a security precaution, to inhibit buyers from cleaning out your entire inventory in case of inadvertent misconfiguration allowing unintentionally-free products. The "Let buyer edit quantity" setting will take effect for products with a non-zero price.



When quantity>1 for a Send Stored Codes product, we issue as many lines from that product's list of codes as the quantity ordered. In our integration POSTs, multiple codes issued would also be delimited by newline characters, e.g.:



num_cart_item = 2

[item_name1] => Picture 2

[item_number1] => XXXXX

[mc_gross_1] => 0

[quantity1] => 1

[key1] => XXXXXX

YYYYYY

[item_name2] => Picture 1

[item_number2] => XXXXX

[mc_gross_2] => 0

[quantity2] => 1

[key2] => XXXXXX

YYYYYY



(It looks a bit weird formatted like that, since that's a generated representation of the raw name=value pairs that are POSTed, but hopefully you get the gist.)