{"id":3142,"date":"2025-09-19T10:51:21","date_gmt":"2025-09-19T01:51:21","guid":{"rendered":"https:\/\/uapisupport.travelport.co.kr\/?page_id=3142"},"modified":"2025-09-23T13:24:32","modified_gmt":"2025-09-23T04:24:32","slug":"request-for-uapi-production-certificate","status":"publish","type":"page","link":"https:\/\/uapisupport.travelport.co.kr\/?page_id=3142","title":{"rendered":"\ubcf8\uc0ac Certificate \uc218\uc815 \uc694\uccad \ub0b4\uc6a9"},"content":{"rendered":"\n

Request for uAPI production Certificate – Updated<\/h2>\n\n\n\n

\u25a0 LowFareSearchReq<\/h2>\n\n\n\n

\u25cf SearchPassenger\/@Age: You have not used age attribute for infant passenger, although you have used it for child passenger. For child and infant its mandatory to use the age attribute.
=> \uc18c\uc544, \uc720\uc544 \ubaa8\ub450 Age\ub97c \ub123\uc5b4 \uc8fc\uc138\uc694.<\/p>\n\n\n\n


If age of the child or infant is not known at this stage a default age of 8 or 9 years for child and 1 year for infant can be sent, which can be corrected to the correct age during booking. This is required in all the requests \u2013 LowFareSearchReq, AirPriceReq and AirCreateReservationReq.
\uc774 \ub2e8\uacc4\uc5d0\uc11c \uc5b4\ub9b0\uc774 \ub610\ub294 \uc720\uc544\uc758 \uc5f0\ub839\uc744 \uc54c \uc218 \uc5c6\ub294 \uacbd\uc6b0 \uae30\ubcf8 \uc5b4\ub9b0\uc774 8 ~ 9 \uc138, \uc720\uc544 1\uc138\ub97c \ub123\uc744 \uc218 \uc788\uc73c\uba70, \uc774\ub294 \ubaa8\ub4e0 \uc694\uccad (LowFareSearchReq, AirPriceReq \ubc0f AirCreateReservationReq)\uc5d0 \ud544\uc694\ud569\ub2c8\ub2e4.
<\/p>\n\n\n\n

\u25cb \uac1c\ubc1c\uc0ac \uc791\uc5c5: \n<com:SearchPassenger Code=\"CNN\" Age=\"8\"\/>\n<com:SearchPassenger Code=\"INF\"\/>\n\uf0f0\t\uc544\ub798\uc640 \uac19\uc774  \uc218\uc815 \ud544\uc694\n<com:SearchPassenger Code=\"CNN\" Age=\"08\"\/>\n<com:SearchPassenger Code=\"INF\" Age=\"01\"\/><\/pre><\/div>\n\n\n\n
\u25cf SearchAirLeg\/SearchOrigin\/@Airport- I have noticed you are using only Airport, is there any specific reason for this. As if Airport is sent (eg: LCY) only the matching airport will be returned and not multi airport city options (eg LHR, LGW, LCY, STN multi-airports for city LON). Hence \u201cCityOrAirport\u201d element can be used when it is not known whether the value is an airport or a city code.
\uc870\ud68c\ub41c \uacf5\ud56d\ub9cc \ub098\uc624\uac8c \uc0ac\uc6a9 \ub418\uc5c8\uc2b5\ub2c8\ub2e4.\ud2b9\ubcc4\ud55c \uc774\uc720\uac00 \uc788\uc2b5\ub2c8\uae4c?
\uacf5\ud56d\uc774 \uc804\uc1a1\ub418\ub294 \uac83\ucc98\ub7fc (\uc608 : LCY) \uc77c\uce58\ud558\ub294 \uacf5\ud56d \ub9cc \ubc18\ud658\ub418\uba70 \ub2e4\uc911 \uacf5\ud56d \ub3c4\uc2dc \uc635\uc158 (\uc608 : LHR, LGW, LCY, \ub3c4\uc2dc LON\uc758 STN \ub2e4\uc911 \uacf5\ud56d)\uc774 \uc544\ub2d9\ub2c8\ub2e4. \ub530\ub77c\uc11c “CityOrAirport”\uc694\uc18c\ub294 \uac12\uc774 \uacf5\ud56d\uc778\uc9c0 \ub610\ub294 \ub3c4\uc2dc \ucf54\ub4dc\uc778\uc9c0 \uc54c \uc218 \uc5c6\uc744 \ub54c \uc0ac\uc6a9\ud560 \uc218 \uc788\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n
\u25cf FlightType: You are using @NonStopDirects and @StopDirects to as true which will return both non-stop and direct flights\/price options, so is there any reason of using them as \u201ctrue\u201d.
Triple Online and Interline Connections are NOT offered through Universal API even though the attributes exist in the schema, so do not use these attributes in the request.
@NonStopDirects \ubc0f @StopDirects\ub97c true\ub85c \uc0ac\uc6a9\ud558\uba74 non-stop \uacfc \uc9c1\ud56d \ubc18\ud658\ub418\ub294\ub370 “true”\ub85c \uc0ac\uc6a9\ud558\ub294 \uc774\uc720\uac00 \uc788\uc2b5\ub2c8\uae4c?
\uc18d\uc131\uc774 \uc2a4\ud0a4\ub9c8\uc5d0 \uc874\uc7ac\ud558\ub354\ub77c\ub3c4 Universal API\ub97c \ud1b5\ud574 TripleOnlineCon \ubc0f SingleInterlineCon \uc774 \uc81c\uacf5\ub418\uc9c0 \uc54a\uc73c\ubbc0\ub85c \uc694\uccad\uc5d0 \uc774\ub7ec\ud55c \uc18d\uc131\uc744 \uc0ac\uc6a9\ud558\uc9c0 \ub9c8\uc2ed\uc2dc\uc624.<\/p>\n\n\n\n
Also Galileo ignore the RequireSingleCarrier, MaxConnections, and MaxStops attributes. Furthermore, you can find detailed information on below link:
\ub610\ud55c Galileo\ub294 RequireSingleCarrier, MaxConnections \ubc0f MaxStops \uc18d\uc131\uc744 \ubb34\uc2dc\ud569\ub2c8\ub2e4. \ub610\ud55c \uc544\ub798 \ub9c1\ud06c\uc5d0\uc11c \uc790\uc138\ud55c \uc815\ubcf4\ub97c \ucc3e\uc744 \uc218 \uc788\uc2b5\ub2c8\ub2e4.
https:\/\/support.travelport.com\/webhelp\/uapi\/uAPI.htm#Air\/Low_Fare_Shopping\/Low_Fare_Shopping_Air_Search_Modifiers.htm?Highlight=flighttype<\/p>\n\n\n\n
<air:FlightType TripleInterlineCon=\"false\" DoubleInterlineCon=\"false\" SingleInterlineCon=\"true\" TripleOnlineCon=\"true\" DoubleOnlineCon=\"true\" SingleOnlineCon=\"true\" StopDirects=\"true\" NonStopDirects=\"true\" \n    MaxStops=\"-1\" MaxConnections=\"-1\" RequireSingleCarrier=\"false\"\/>\n\u25cb \uc218\uc815: \n<air:FlightType TripleInterlineCon=\"false\" DoubleInterlineCon=\"false\" SingleInterlineCon=\"false\" TripleOnlineCon=\"false\" DoubleOnlineCon=\"true\" SingleOnlineCon=\"false\" StopDirects=\"true\" NonStopDirects=\"true\" \/><\/pre><\/div>\n\n\n\n
\u25cb To return both non-stop and direct flights\/price options, set both @NonStopDirects and @StopDirects to true.
\u25cb Galileo and Apollo ignore the RequireSingleCarrier, MaxConnections, and MaxStops attributes.<\/p>\n\n\n\n
\u25a0 AirPriceReq<\/h2>\n\n\n\n
\u25cf @AuthorizedBy: Though AuthorizedBy is an optional attribute, still it is recommended adding the appropriate value for AuthorizedBy throughout the workflow. This can be useful to identify the application\/agent who made the booking.
AuthorizedBy\ub294 \uc120\ud0dd\uc801 \uc18d\uc131\uc774\uc9c0\ub9cc \uc6cc\ud06c \ud50c\ub85c\uc6b0 \uc804\uccb4\uc5d0 AuthorizedBy\uc5d0 \uc801\uc808\ud55c \uac12\uc744 \ucd94\uac00\ud558\ub294 \uac83\uc774 \uc88b\uc2b5\ub2c8\ub2e4. \uc608\uc57d \ud55c \uc751\uc6a9 \ud504\ub85c\uadf8\ub7a8 \/ \uc5d0\uc774\uc804\ud2b8\ub97c \uc2dd\ubcc4\ud558\ub294 \ub370 \uc720\uc6a9 \ud560 \uc218 \uc788\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n
\u25cb \uac1c\ubc1c\uc0ac: \n<air:AirPriceReq CheckFlightDetails=\"true\" FareRuleType=\"short\" TargetBranch=\"P***6537\" TraceId=\"OTTE_1G\">\n\u25cb \uc218\uc815:  \n<air:AirPriceReq CheckFlightDetails=\"true\" FareRuleType=\"short\" TargetBranch=\"P***537\" AuthorizedBy=\"OTTE_1G\" TraceId=\"202004231144123\"><\/pre><\/div>\n\n\n\n
\u25cf SearchPassenger\/@Age: Age is required for both Child and Infant passenger type to get correct fare for both the PTCs. Same Age as used in LowFareSearchReq must be used in AirPriceReq.
\uc5b4\ub9b0\uc774\uc640 \uc720\uc544 \uc2b9\uac1d \uc720\ud615 \ubaa8\ub450 PTC\uc5d0 \ub300\ud574 \uc62c\ubc14\ub978 \uc694\uae08\uc744 \ubc1b\uc73c\ub824\uba74 \uc5f0\ub839\uc774 \ud544\uc694\ud569\ub2c8\ub2e4. LowFareSearchReq\uc5d0\uc11c \uc0ac\uc6a9 \ub41c \uac83\uacfc \ub3d9\uc77c\ud55c \uc5f0\ub839\uc774 AirPriceReq\uc5d0\uc11c \uc0ac\uc6a9\ub418\uc5b4\uc57c\ud569\ub2c8\ub2e4.<\/p>\n\n\n\n
\u25cb \uac1c\ubc1c\uc0ac: <com:SearchPassenger BookingTravelerRef=\"CHD1\" Code=\"CHD\"\/>\n       <com:SearchPassenger BookingTravelerRef=\"INF1\" Code=\"INF\"\/>\n\u25cb \uc218\uc815: <com:SearchPassenger BookingTravelerRef=\"CHD1\" Code=\"CHD\" Age=\"08\"\/>\n       <com:SearchPassenger BookingTravelerRef=\"INF1\" Code=\"INF\" Age=\"01\"\/> <\/pre><\/div>\n\n\n\n
1) AirPricingModifiers@InventoryRequestType – I notice that you have used InventoryRequestType=”Basic” in your request. Since you are using permitted booking codes in your request, you should use InventoryRequestType=”DirectAccess” for AirPriceReq to validate the availability. You can get detailed information below:
https:\/\/support.travelport.com\/webhelp\/uapi\/uAPI.htm#Air\/Air_Pricing\/Air_Pricing_with_Inventory_Options.htm?Highlight=InventoryRequestType<\/p>\n\n\n\n
2) AirPricingModifiers@CurrencyType – You have used CurrencyType=”KRW” in your request. The CurrencyType in AirPricingModifiers is passed to the provider, which affects the currency that is returned for Equivalent Base Price, Base Price, Taxes, and Total Price. In your case default currency for the PCC is KRW, which is same as the currency type used in AirPriceReq. So there is no need to use CurrencyType in AirPriceReq.<\/p>\n\n\n\n
3) AirPricingModifiers@PlatingCarrier – I see that you are using PlatingCarrier in AirPricingModifiers in your request. There is default plating carrier logic on your PCC as per your PCC settings, so there is no need to use this attribute.<\/p>\n\n\n\n
4) Key in SearchPassenger – I notice that you are using Key in SearchPassenger for all passengers. It is not required to use key. BookingTravelerRef is sufficient to be passed. BookingTravelerRef value should be set for Multiple Passengers in the request.<\/p>\n\n\n\n
AirSegment – Connection Indicator – This is still not implemented. Please note that it is mandatory to include connection indicator for connecting flights. Please see the details in my feedback earlier.
\ucee4\ub125\ud305 \uc5ec\uc815\uc5d0\ub294\u201d Connection Indicator\u201d \uc0ac\uc6a9\uc774 \ud544\uc218\uc774\ub2c8 \uaf2d \uc0ac\uc6a9\ud574\uc8fc\uc138\uc694.<\/p>\n\n\n\n
AirPricingModifiers@FaresIndicator – This is still not implemented. It is recommended to use FaresIndicator for all transactions to indicate fare types to be sent in the request. You have used it in LFS request but not in AirPriceReq.
LFS \uc694\uccad\uc5d0\uc11c\ub294 \uc0ac\uc6a9\ud588\uc9c0\ub9cc AirPriceReq\uc5d0\ub294 \uc0ac\uc6a9\ud558\uc9c0 \uc54a\uc558\uc2b5\ub2c8\ub2e4. \ubaa8\ub4e0 \uac70\ub798\uc5d0 \ub300\ud574 FaresIndicator\ub97c \uc0ac\uc6a9\ud558\uc5ec \uc694\uccad\uc5d0\uc11c \ubcf4\ub0bc \uc694\uae08 \uc720\ud615\uc744 \ud45c\uc2dc\ud574\uc8fc\uc138\uc694.<\/p>\n\n\n\n
AirPricingModifiers@InventoryRequestType – This is also not implemented yet. As you are using permitted booking code then inventory type attribute should be passed in the request under AirPricingModifiers InventoryRequestType=”DirectAccess” for AirPriceReq to validate the availability
Permitted booking code\ub97c \uc0ac\uc6a9\ud558\uace0 \uc788\uc73c\ubbc0\ub85c AirPriceReq\uc758 \uac00\uc6a9\uc131\uc744 \ud655\uc778\ud558\ub824\uba74 AirPriceReq\uc5d0\uc11c AirPricingModifiers InventoryRequestType=”DirectAccess” \uc544\ub798\uc758 \uc694\uccad\uc5d0 \uc778\ubca4\ud1a0\ub9ac \uc720\ud615 \uc18d\uc131\uc744 \uc804\ub2ec\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n
\u25a0 AirCreateReservationReq<\/h2>\n\n\n\n
\u25cf RetainReservation: You have used RetainReservation=”Both” in your request, which means PNR is created even when schedule and price have changed and AirSolutionChangedInfo returns original time and price.
In your case AirSolutionChangedInfo is not returned, which means there is no price or schedule change.
\uc694\uccad\uc5d0 RetainReservation = “Both”\ub97c \uc0ac\uc6a9\ud588\uc2b5\ub2c8\ub2e4. \uc774\ub294 \uc77c\uc815\uacfc \uac00\uaca9\uc774 \ubcc0\uacbd\ub418\uace0 AirSolutionChangedInfo\uac00 \uc6d0\ub798 \uc2a4\ucf00\uc974\uacfc \uac00\uaca9\uc744 \ubc18\ud658\ud558\ub354\ub77c\ub3c4 PNR\uc774 \uc0dd\uc131\ub428\uc744 \uc758\ubbf8\ud569\ub2c8\ub2e4.
\uadc0\ud558\uc758 \uacbd\uc6b0 AirSolutionChangedInfo\uac00 \ubc18\ud658\ub418\uc9c0 \uc54a\uc73c\ubbc0\ub85c \uac00\uaca9\uc774\ub098 \uc77c\uc815\uc774 \ubcc0\uacbd\ub418\uc9c0 \uc54a\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n
Could you please explain since you are using RetainReservation as “both”, how you would be handling the situation if you have schedule change, incomplete booking with segment failure or price change scenario?
RetainReservation\uc744 “Both”\ub85c \uc0ac\uc6a9\ud558\uace0 \uc788\uae30 \ub54c\ubb38\uc5d0 \uc77c\uc815 \ubcc0\uacbd, \uc138\uadf8\uba3c\ud2b8 \uc2e4\ud328\ub85c \uc778\ud55c \ubd88\uc644\uc804\ud55c \uc608\uc57d \ub610\ub294 \uac00\uaca9 \ubcc0\uacbd \uc2dc\ub098\ub9ac\uc624\uac00 \uc788\ub294 \uacbd\uc6b0 \uc0c1\ud669\uc744 \ucc98\ub9ac\ud558\ub294 \ubc29\ubc95\uc744 \uc124\uba85\ud574 \uc8fc\uc2dc\uaca0\uc2b5\ub2c8\uae4c?<\/p>\n\n\n\n
You can find more details on RetainReservation attribute here:
https:\/\/support.travelport.com\/webhelp\/uapi\/uAPI.htm#Air\/Air_Booking\/Create_Air_Booking\/Creating_Air_Bookings.htm?Highlight=RetainReservation<\/p>\n\n\n\n
\u25cb \uac1c\ubc1c\uc0ac:  \n<univ:AirCreateReservationReq RetainReservation=\"Both\" TargetBranch=\"P****\" AuthorizedBy=\"user\" TraceId=\"OTTE_1G\"><\/pre><\/div>\n\n\n\n
1) AirPricingModifiers\/@InventoryRequestType: As you are using permitted booking code then inventory type attribute is required to be passed in the request under AirPricingModifiers InventoryRequestType=”DirectAccess” for AirPriceReq to validate the availability.<\/p>\n\n\n\n
\u25cf BookingTraveler@NameRemark \u2013 You have not included NameRemarks for INF booking traveler in your request. Name remarks are recommended for INF and CNN. You can check more details on name remarks here:
\uadc0\ud558\uc758 \uc694\uccad\uc5d0 INF \uc608\uc57d \uc5ec\ud589\uc790\uc5d0 \ub300\ud55c NameRemarks\ub97c \ud3ec\ud568\uc2dc\ud0a4\uc9c0 \uc54a\uc558\uc2b5\ub2c8\ub2e4. INF \ubc0f CNN\uc5d0\ub294 \uc774\ub984 \uc124\uba85\uc774 \uad8c\uc7a5\ub429\ub2c8\ub2e4. \uc774\ub984 \uc124\uba85\uc5d0 \ub300\ud55c \uc790\uc138\ud55c \ub0b4\uc6a9\uc740 \uc5ec\uae30\ub97c \ucc38\uc870\ud558\uc2ed\uc2dc\uc624.
https:\/\/support.travelport.com\/webhelp\/uapi\/uAPI.htm#Booking\/Shared_Topics\/Name_Remarks.htm<\/p>\n\n\n\n
\u25cb \uac1c\ubc1c\uc0ac : <com:BookingTraveler Gender=\"M\" TravelerType=\"INF\" DOB=\"2019-01-01\" Age=\"2\">\n   <com:BookingTravelerName Prefix=\"MSTR\" Last=\"KIM\" First=\"HAZI\"\/>\n<\/com:BookingTraveler>\n\n\u25cb \uc218\uc815: <com:BookingTraveler Gender=\"M\" TravelerType=\"INF\" DOB=\"2019-01-01\" Age=\"2\">\n   <com:BookingTravelerName Prefix=\"MSTR\" Last=\"KIM\" First=\"HAZI\"\/>\n   <com:NameRemark>\n      <com:RemarkData>INF\uc5d0 \ud544\uc694\ud55c 1G \ub0b4\uc6a9\/\ud5ec\ud504\uc5d0 \ubb38\uc758 <\/com:RemarkData>\n    <\/com:NameRemark>\n<\/com:BookingTraveler><\/pre><\/div>\n\n\n\n
Format for child and infant name remarks:\n\nChild NameRemark\n<NameRemark>\n<RemarkData>P-C08 DOB20MAR14<\/RemarkData>\n<\/NameRemark>\n\nInfant NameRemark\n<NameRemark>\n<RemarkData>28FEB21<\/RemarkData>\n<\/NameRemark>\n<\/pre><\/div>\n\n\n\n
CHD\ub294 CREATE \uc2dc \ubc18\ub4dc\uc2dc CNN Age \uc9c0\uc815 => <air:PassengerType BookingTravelerRef=\u201dCNN01\u2033 Code=\u201dCNN\u201d Age=\u201d9\u2033 \/><\/p>\n\n\n\n
\u25cf SSR: I noticed you have not provided SSR for child and infant. Please include the same as its required by some carriers\/sectors. See the example below:
\uc5b4\ub9b0\uc774 \ubc0f \uc720\uc544\uc5d0\uac8c SSR\uc744 \uc81c\uacf5\ud558\uc9c0 \uc54a\uc740 \uac83\uc73c\ub85c \ub098\ud0c0\ub0ac\uc2b5\ub2c8\ub2e4. \ub3d9\uc77c \ud56d\uacf5\uc0ac\/\uad6c\uac04 \uc5d0\uc11c \uc694\uad6c\ud558\ub294 \uac83\uacfc \ub3d9\uc77c\ud558\uac8c \ud3ec\ud568\ud558\uc2ed\uc2dc\uc624. \uc544\ub798 \uc608\ub97c \ucc38\uc870\ud558\uc2ed\uc2dc\uc624.

Gender for infant should be with additional “I”, MI – Male infant, FI \u2013 Female infant.<\/p>\n\n\n\n
\u25cf AirPricingSolution – You have only passed key in AirPricingSolution. Complete AirPricingSolution information must be passed in AirCreateReservationReq as returned in AirPriceRsp, including the pricing information.
AirPricingSolution\uc758 \ud0a4\ub9cc \uc804\ub2ec\ud588\uc2b5\ub2c8\ub2e4. \uc694\uae08 \uc815\ubcf4\ub97c \ud3ec\ud568\ud558\uc5ec AirPriceRsp\uc5d0 \ubc18\ud658 \ub41c\ub300\ub85c \uc644\uc804\ud55c AirPricingSolution \uc815\ubcf4\ub97c AirCreateReservationReq\ub85c \uc804\ub2ec\ud574\uc57c \ud569\ub2c8\ub2e4.<\/p>\n\n\n\n
AirPricingSolution@AirPricingInfo – I can see that you are not passing the complete pricing information as received in AirPriceRsp. It is recommended to pass complete information to avoid any fare issues.
AirPriceRsp\uc5d0 \uc811\uc218 \ub41c\ub300\ub85c \uc804\uccb4 \uac00\uaca9 \uc815\ubcf4\ub97c \uc804\ub2ec\ud558\uc9c0 \uc54a\uc558 \uc74c\uc744 \uc54c \uc218 \uc788\uc2b5\ub2c8\ub2e4. \uc6b4\uc784 \ubb38\uc81c\ub97c \ud53c\ud558\uae30 \uc704\ud574 \uc644\uc804\ud55c \uc815\ubcf4\ub97c \uc804\ub2ec\ud558\ub294 \uac83\uc774 \uc88b\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n
Price Check: We would recommend implementing a price check, to ensure to receive a price from search and keep the same price in air pricing and air create.
\uac80\uc0c9\uc5d0\uc11c \uac00\uaca9\uc744 \ubc1b\uace0 \ud56d\uacf5 \uac00\uaca9 \uc0dd\uc131\uc2dc \ub3d9\uc77c\ud55c \uac00\uaca9\uc744 \uc720\uc9c0\ud558\ub824\uba74 \uac00\uaca9 \ud655\uc778\uc744 \uad6c\ud604\ud558\ub294 \uac83\uc774 \uc88b\uc2b5\ub2c8\ub2e4.<\/p>\n\n\n\n
Order of booking travelers: It is recommended to book the infant connected to an adult, so you would add the BookingTravelers in the following order: Adult, Infant, Child
\uc131\uc778\uacfc \uc5f0\uacb0\ub41c \uc720\uc544\ub97c \uc608\uc57d\ud558\ub294 \uac83\uc774 \uc88b\uc2b5\ub2c8\ub2e4. \ub530\ub77c\uc11c BookingTravelers\ub97c \uc131\uc778, \uc720\uc544, \uc5b4\ub9b0\uc774 \uc21c\uc11c\ub85c \ucd94\uac00\ud558\uc2ed\uc2dc\uc624.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Request for uAPI production Certificate – Updated \u25a0 LowFareSearchReq \u25cf SearchPassenger\/@Age: You have not used age attribute for infant passenger, although you have used it for child passenger. For child and infant its mandatory to use the age attribute.=> \uc18c\uc544, \uc720\uc544 \ubaa8\ub450 Age\ub97c \ub123\uc5b4 \uc8fc\uc138\uc694. If age of the child or infant is not known …
\ubcf8\uc0ac Certificate \uc218\uc815 \uc694\uccad \ub0b4\uc6a9<\/span> \ub354\ubcf4\uae30<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-3142","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/pages\/3142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3142"}],"version-history":[{"count":7,"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/pages\/3142\/revisions"}],"predecessor-version":[{"id":3155,"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=\/wp\/v2\/pages\/3142\/revisions\/3155"}],"wp:attachment":[{"href":"https:\/\/uapisupport.travelport.co.kr\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}